Re: IFL's, VM, and Linux
Hi everyone. We think we saw a difference in behaviour between these two versions. It appeared to us that we had to specify both CPU values on one card to get the desired effect. If pressed however I will deny it. Edward Long --- On Tue, 7/27/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Tuesday, July 27, 2010, 12:15 AM On Monday, 07/26/2010 at 12:55 EDT, Sam Bass sam.b...@mclaneco.com wrote: I guess I don't understand the difference between VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL And VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 This is a q vconfig looks like q vconfig MODE = LINUX If you're running in a Linux mode LPAR with IFLs, there IS no difference. Go look at the table on the DEFINE CPU command. The problem, as Mark Pace pointed out, pops up when you're in a z/VM mode LPAR. The first one shown above will work in all cases, even though it isn't always necessary. And I agree with Mark Post that the above should be changed to be CPU 00 and 01 for simplicity and clarity. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On Tuesday, 07/27/2010 at 12:13 EDT, Ed Long rdhm...@prodigy.net wrote: We think we saw a difference in behaviour between these two versions. It appeared to us that we had to specify both CPU values on one card to get the desired effect. If pressed however I will deny it. :-) It depends. If you are in virtual configuration mode (VCONFIG) LINUX or ESA390, then all CPUs have to be the same type and you have to specify ALL virtual CPUs on the same DEFINE CPU command. If you are VCONFIG VM, then you can have mixed CPU types and you can specify the CPUs on separate DEFINE CPU commands. I should point out, too, that you don't really need the CPU statements at all. COMMAND DEFINE CPU will create the virtual CPUs you need. I.e.: COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 00 01 02 03 TYPE IFL MACHINE ESA 4 is all you need. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Does this mean that CPU 02 and 03 are unavailable for any other z/VM guest? Sam Bass -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Ed Long Sent: Friday, July 23, 2010 2:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: IFL's, VM, and Linux Progress reported. We reread the entireVM listserv item as suggested. The following sequence added to the user directory appears to accomplish what we are trying to do. Linux is still under VM. We proved it by installing a fractal generator and watching it run. Seemed like I was back in college! VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL Thanks for the assist. Sugg to the IBM'ers, the doc on this subject could stand an upgrade. Edward Long --- On Fri, 7/23/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Friday, July 23, 2010, 10:48 AM Hi everyone. Back in April on the VM user group someone asked this very question. Here is what they said: *BEGIN EXCERPT Yes. Do CP DEDICATE USER userid CPU cpuaddr. Or add DEDICATE to the CPU directory statement. *END EXCERPT We will test whether this command forces the zLinux workload onto the IFL. Edward Long --- On Thu, 7/22/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:59 AM Thank you for the clarifications. The VM LPAR in question is also running a z/OS guest hence the need to allocate the real CP's. From the HMC profile perspective, all the engines are shared among all the LPAR's. Re John S.'s question, we used the VM performance toolkit to observe a WAS/Linux workload and could see the work only dispatching on the CP's. I will report back when we get more info. Thank you all for the assistance. Edward Long --- On Thu, 7/22/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:15 AM On Wednesday, 07/21/2010 at 05:20 EDT, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). No. A z/VM *mode* LPAR on a z10 or zEnterprise has separate pools of CPs, IFLs, ICFs, zIIPs, and zAAPs at its disposal, depending on what's in the LPAR activation profile. By placing the IFL keyword on DEFINE CPU, you tell CP to use a real IFL out of the pool when it dispatches the guest. The guest could be dispatched on any available IFL. If you SET CPUAFFINITY OFF for the user (default is ON), all of the virtual CPUs will be dispatched on the primary CPU type (CP's for a z/VM mode LPAR). And Ray is correct - in a z/VM mode LPAR you need COMMAND SET VCONFIG MODE LINUX first. Look at the table in the DEFINE CPU command. (VCONFIG MODE ESA/390 is the default for non-Linux-only LPARs.) The relationship between the LPAR *mode*, as defined in the image profile (ESA/390, Linux, z/VM), and the valid primary and secondary CPU types is part of the machine architecture and is important to understand. It can seem a little strange until you realize that the purpose of this part of the architecture is to ensure that an LPAR's CPU configuration (a) is useful, (b) avoids abends, and (c) ensures workloads run on the CPUs they are licensed for. The SET VCONFIG command simulates the LPAR configuration mode and so the virtual CPU configuration is dictated. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IFL's, VM, and Linux
The CPU's in the user directory are virtual ones, not related to real CPU's in any way. Best regards, Pieter Harder pieter.har...@brabantwater.nl tel +31-73-6837133 / +31-6-47272537 -Oorspronkelijk bericht- Van: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Namens Sam Bass Verzonden: maandag 26 juli 2010 18:16 Aan: LINUX-390@VM.MARIST.EDU Onderwerp: Re: IFL's, VM, and Linux Does this mean that CPU 02 and 03 are unavailable for any other z/VM guest? Sam Bass -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Ed Long Sent: Friday, July 23, 2010 2:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: IFL's, VM, and Linux Progress reported. We reread the entireVM listserv item as suggested. The following sequence added to the user directory appears to accomplish what we are trying to do. Linux is still under VM. We proved it by installing a fractal generator and watching it run. Seemed like I was back in college! VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL Thanks for the assist. Sugg to the IBM'ers, the doc on this subject could stand an upgrade. Edward Long --- On Fri, 7/23/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Friday, July 23, 2010, 10:48 AM Hi everyone. Back in April on the VM user group someone asked this very question. Here is what they said: *BEGIN EXCERPT Yes. Do CP DEDICATE USER userid CPU cpuaddr. Or add DEDICATE to the CPU directory statement. *END EXCERPT We will test whether this command forces the zLinux workload onto the IFL. Edward Long --- On Thu, 7/22/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:59 AM Thank you for the clarifications. The VM LPAR in question is also running a z/OS guest hence the need to allocate the real CP's. From the HMC profile perspective, all the engines are shared among all the LPAR's. Re John S.'s question, we used the VM performance toolkit to observe a WAS/Linux workload and could see the work only dispatching on the CP's. I will report back when we get more info. Thank you all for the assistance. Edward Long --- On Thu, 7/22/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:15 AM On Wednesday, 07/21/2010 at 05:20 EDT, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). No. A z/VM *mode* LPAR on a z10 or zEnterprise has separate pools of CPs, IFLs, ICFs, zIIPs, and zAAPs at its disposal, depending on what's in the LPAR activation profile. By placing the IFL keyword on DEFINE CPU, you tell CP to use a real IFL out of the pool when it dispatches the guest. The guest could be dispatched on any available IFL. If you SET CPUAFFINITY OFF for the user (default is ON), all of the virtual CPUs will be dispatched on the primary CPU type (CP's for a z/VM mode LPAR). And Ray is correct - in a z/VM mode LPAR you need COMMAND SET VCONFIG MODE LINUX first. Look at the table in the DEFINE CPU command. (VCONFIG MODE ESA/390 is the default for non-Linux-only LPARs.) The relationship between the LPAR *mode*, as defined in the image profile (ESA/390, Linux, z/VM), and the valid primary and secondary CPU types is part of the machine architecture and is important to understand. It can seem a little strange until you realize that the purpose of this part of the architecture is to ensure that an LPAR's CPU configuration (a) is useful, (b) avoids abends, and (c) ensures workloads run on the CPUs they are licensed for. The SET VCONFIG command simulates the LPAR configuration mode and so the virtual CPU configuration is dictated. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IFL's, VM, and Linux
On Monday, 07/26/2010 at 12:17 EDT, Sam Bass sam.b...@mclaneco.com wrote: Does this mean that CPU 02 and 03 are unavailable for any other z/VM guest? No. Those are *virtual* CPU definitions. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
I guess I don't understand the difference between VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL And VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 This is a q vconfig looks like q vconfig MODE = LINUX -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
The 1st option is if you are running in an LPAR with mixed CPU types, CP IFL. The first option ensures that your Linux guest runs on an IFL. By default it will run on a CP. On Mon, Jul 26, 2010 at 12:54 PM, Sam Bass sam.b...@mclaneco.com wrote: I guess I don't understand the difference between VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL And VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 This is a q vconfig looks like q vconfig MODE = LINUX -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On 7/26/2010 at 12:19 PM, Alan Altmark alan_altm...@us.ibm.com wrote: On Monday, 07/26/2010 at 12:17 EDT, Sam Bass sam.b...@mclaneco.com wrote: Does this mean that CPU 02 and 03 are unavailable for any other z/VM guest? No. Those are *virtual* CPU definitions. Which also means that you don't need to have them be CPU 02 and CPU 03. If you have them as CPU 00 and CPU 01, it will work just the same, and be less confusing to anyone else that looks at the definitions. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On Monday, 07/26/2010 at 12:55 EDT, Sam Bass sam.b...@mclaneco.com wrote: I guess I don't understand the difference between VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL And VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 This is a q vconfig looks like q vconfig MODE = LINUX If you're running in a Linux mode LPAR with IFLs, there IS no difference. Go look at the table on the DEFINE CPU command. The problem, as Mark Pace pointed out, pops up when you're in a z/VM mode LPAR. The first one shown above will work in all cases, even though it isn't always necessary. And I agree with Mark Post that the above should be changed to be CPU 00 and 01 for simplicity and clarity. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Thank you all very much for the great assistance. Now, to continue the quote from Casablanca, Where are my winnings? I will pop a note as suggested. Edward Long --- On Fri, 7/23/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Friday, July 23, 2010, 5:58 PM On Friday, 07/23/2010 at 03:05 EDT, Ed Long rdhm...@prodigy.net wrote: Sugg to the IBM'ers, the doc on this subject could stand an upgrade. I'm shocked, Ed. Shocked, I say. It's intuitively obvious as long as you understand o LPAR configuration modes o Primary and secondary CPUs o The DEFINE CPU command o The SET VCONFIG command o The CPU statement in the directory o The COMMAND statement in the directory and all that it implies o CPU affinitiy o The relationships among the above What could be easier? (I know - almost anything else.) ;-) We did indeed do a poor job of making this understandable. :-( Needless to say, you are not the first person to trip over this. As usual, please send e-mail to mhvr...@us.ibm.com (aka submit a Reader's Comment Form) so that the writers can get working on it. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Hi everyone. Back in April on the VM user group someone asked this very question. Here is what they said: *BEGIN EXCERPT Yes. Do CP DEDICATE USER userid CPU cpuaddr. Or add DEDICATE to the CPU directory statement. *END EXCERPT We will test whether this command forces the zLinux workload onto the IFL. Edward Long --- On Thu, 7/22/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:59 AM Thank you for the clarifications. The VM LPAR in question is also running a z/OS guest hence the need to allocate the real CP's. From the HMC profile perspective, all the engines are shared among all the LPAR's. Re John S.'s question, we used the VM performance toolkit to observe a WAS/Linux workload and could see the work only dispatching on the CP's. I will report back when we get more info. Thank you all for the assistance. Edward Long --- On Thu, 7/22/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:15 AM On Wednesday, 07/21/2010 at 05:20 EDT, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). No. A z/VM *mode* LPAR on a z10 or zEnterprise has separate pools of CPs, IFLs, ICFs, zIIPs, and zAAPs at its disposal, depending on what's in the LPAR activation profile. By placing the IFL keyword on DEFINE CPU, you tell CP to use a real IFL out of the pool when it dispatches the guest. The guest could be dispatched on any available IFL. If you SET CPUAFFINITY OFF for the user (default is ON), all of the virtual CPUs will be dispatched on the primary CPU type (CP's for a z/VM mode LPAR). And Ray is correct - in a z/VM mode LPAR you need COMMAND SET VCONFIG MODE LINUX first. Look at the table in the DEFINE CPU command. (VCONFIG MODE ESA/390 is the default for non-Linux-only LPARs.) The relationship between the LPAR *mode*, as defined in the image profile (ESA/390, Linux, z/VM), and the valid primary and secondary CPU types is part of the machine architecture and is important to understand. It can seem a little strange until you realize that the purpose of this part of the architecture is to ensure that an LPAR's CPU configuration (a) is useful, (b) avoids abends, and (c) ensures workloads run on the CPUs they are licensed for. The SET VCONFIG command simulates the LPAR configuration mode and so the virtual CPU configuration is dictated. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On Friday, 07/23/2010 at 10:51 EDT, Ed Long rdhm...@prodigy.net wrote: Hi everyone. Back in April on the VM user group someone asked this very question. Here is what they said: *BEGIN EXCERPT Yes. Do CP DEDICATE USER userid CPU cpuaddr. Or add DEDICATE to the CPU directory statement. *END EXCERPT We will test whether this command forces the zLinux workload onto the IFL. That isn't going to work, Ed. You can only dedicate *primary* CPUs, not secondaries. In a z/VM mode LPAR, the primary CPU type is CP. You need to use the SET VCONFIG and DEFINE CPU statements as previously discussed in this thread. The only time you can DEDICATE an IFL is when you are running in a LINUX mode LPAR with IFLs. See Usage Note #1 in the help for the CP DEDICATE command. Further, read that other post carefully. DEDICATE is how give an *entire* logical CPU to a *single* virtual machine, making it ineligible to be shared among all virtual machines. If the guest is idle, so will be the dedicated CPU. I view a dedicated CPU as the modern z/VM equivalent of the medieval flail: o It's use seems obvious to the casual observer, o The effect on the intended target is significant and easily observed, o In a crowded room there will be significant collateral damage, o In inexperienced hands, there is a good chance that the wielder will be injured. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Progress reported. We reread the entireVM listserv item as suggested. The following sequence added to the user directory appears to accomplish what we are trying to do. Linux is still under VM. We proved it by installing a fractal generator and watching it run. Seemed like I was back in college! VM Listserve Suggestion MACHINE ESA 2 CPU 02 CPU 03 COMMAND SET VCONFIG MODE LINUX COMMAND DEFINE CPU 02 03 TYPE IFL Thanks for the assist. Sugg to the IBM'ers, the doc on this subject could stand an upgrade. Edward Long --- On Fri, 7/23/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Friday, July 23, 2010, 10:48 AM Hi everyone. Back in April on the VM user group someone asked this very question. Here is what they said: *BEGIN EXCERPT Yes. Do CP DEDICATE USER userid CPU cpuaddr. Or add DEDICATE to the CPU directory statement. *END EXCERPT We will test whether this command forces the zLinux workload onto the IFL. Edward Long --- On Thu, 7/22/10, Ed Long rdhm...@prodigy.net wrote: From: Ed Long rdhm...@prodigy.net Subject: Re: IFL's, VM, and Linux To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:59 AM Thank you for the clarifications. The VM LPAR in question is also running a z/OS guest hence the need to allocate the real CP's. From the HMC profile perspective, all the engines are shared among all the LPAR's. Re John S.'s question, we used the VM performance toolkit to observe a WAS/Linux workload and could see the work only dispatching on the CP's. I will report back when we get more info. Thank you all for the assistance. Edward Long --- On Thu, 7/22/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:15 AM On Wednesday, 07/21/2010 at 05:20 EDT, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). No. A z/VM *mode* LPAR on a z10 or zEnterprise has separate pools of CPs, IFLs, ICFs, zIIPs, and zAAPs at its disposal, depending on what's in the LPAR activation profile. By placing the IFL keyword on DEFINE CPU, you tell CP to use a real IFL out of the pool when it dispatches the guest. The guest could be dispatched on any available IFL. If you SET CPUAFFINITY OFF for the user (default is ON), all of the virtual CPUs will be dispatched on the primary CPU type (CP's for a z/VM mode LPAR). And Ray is correct - in a z/VM mode LPAR you need COMMAND SET VCONFIG MODE LINUX first. Look at the table in the DEFINE CPU command. (VCONFIG MODE ESA/390 is the default for non-Linux-only LPARs.) The relationship between the LPAR *mode*, as defined in the image profile (ESA/390, Linux, z/VM), and the valid primary and secondary CPU types is part of the machine architecture and is important to understand. It can seem a little strange until you realize that the purpose of this part of the architecture is to ensure that an LPAR's CPU configuration (a) is useful, (b) avoids abends, and (c) ensures workloads run on the CPUs they are licensed for. The SET VCONFIG command simulates the LPAR configuration mode and so the virtual CPU configuration is dictated. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On Friday, 07/23/2010 at 03:05 EDT, Ed Long rdhm...@prodigy.net wrote: Sugg to the IBM'ers, the doc on this subject could stand an upgrade. I'm shocked, Ed. Shocked, I say. It's intuitively obvious as long as you understand o LPAR configuration modes o Primary and secondary CPUs o The DEFINE CPU command o The SET VCONFIG command o The CPU statement in the directory o The COMMAND statement in the directory and all that it implies o CPU affinitiy o The relationships among the above What could be easier? (I know - almost anything else.) ;-) We did indeed do a poor job of making this understandable. :-( Needless to say, you are not the first person to trip over this. As usual, please send e-mail to mhvr...@us.ibm.com (aka submit a Reader's Comment Form) so that the writers can get working on it. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Ed, I already submitted one for this, particulary that it is pretty hard to know what you have to put in the directory to get it to be an IFL in a mixed mode box. It was accepted. Not sure if more will help, but FWIW... Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan Altmark Sent: Friday, July 23, 2010 2:58 PM To: LINUX-390@vm.marist.edu Subject: Re: [LINUX-390] IFL's, VM, and Linux On Friday, 07/23/2010 at 03:05 EDT, Ed Long rdhm...@prodigy.net wrote: Sugg to the IBM'ers, the doc on this subject could stand an upgrade. I'm shocked, Ed. Shocked, I say. It's intuitively obvious as long as you understand o LPAR configuration modes o Primary and secondary CPUs o The DEFINE CPU command o The SET VCONFIG command o The CPU statement in the directory o The COMMAND statement in the directory and all that it implies o CPU affinitiy o The relationships among the above What could be easier? (I know - almost anything else.) ;-) We did indeed do a poor job of making this understandable. :-( Needless to say, you are not the first person to trip over this. As usual, please send e-mail to mhvr...@us.ibm.com (aka submit a Reader's Comment Form) so that the writers can get working on it. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Does he also need: COMMAND SET VCONFIG MODE LINUX due to the mixed environment? Ray Mrohs U.S. Department of Justice 202-307-6896 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Wednesday, July 21, 2010 5:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: IFL's, VM, and Linux On 7/21/2010 at 05:16 PM, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? No. This is referring to the virtual CPUs that the guest will see, not the real hardware. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Ed, I think we need to look at your configuration a little deeper. You say that Linux can see all 6 of your real processors. By default VM will give just one virtual processor to a guest. How are you determining that you can get to all 6 processors with Linux? I think you will need to start by looking at the hardware Image profile to see what processors are assigned to the VM Partition? Under most circumstances most customers do not mix the CP's, IFL's and ZAAP's in the same partition unless they are running a VM Mode partition with z/OS as a guest of VM. Regards, John Schnitzler Jr. jnsch...@us.ibm.com From: Ed Long rdhm...@prodigy.net To: LINUX-390@vm.marist.edu Date: 07/21/2010 05:19 PM Subject:Re: IFL's, VM, and Linux Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). Edward Long --- On Wed, 7/21/10, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Wednesday, July 21, 2010, 5:02 PM On 7/21/2010 at 01:21 PM, Ed Long rdhm...@prodigy.net wrote: We have a z10 running VM 5.4 in LPAR #1. The box has 2 half speed CP's, 2 IFL's, and 2 ZAAP's. We want to modify a specific zLinux guest, call it zLinux1, to only run on the IFL's. So far, we can get it to see all 6 engines which is not good. Sorry if this is obvous to some, what would be the best practice for doing this? Can we do it all in the Directory? Yes. Can we do the configuration in such a way that it survives reboots and vm IPL's? Yes. In the USER DIRECT entry for the guest, add COMMAND DEFINE CPU 00 IFL If the Linux system is not consuming more than ~ 80% of a real CPU, it should only have one virtual CPU defined. If it really needs more than that, then add another COMMAND DEFINE CPU xx IFL statement for each one. For this to take effect, you'll need to shutdown the Linux guest and log it off. You could issue the #CP DEFINE CPU 00 IFL command instead, but make sure your Linux guest is all the way down, as it will cause a virtual machine system reset and clear. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ inline: graycol.gif
Re: IFL's, VM, and Linux
On Wednesday, 07/21/2010 at 05:20 EDT, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). No. A z/VM *mode* LPAR on a z10 or zEnterprise has separate pools of CPs, IFLs, ICFs, zIIPs, and zAAPs at its disposal, depending on what's in the LPAR activation profile. By placing the IFL keyword on DEFINE CPU, you tell CP to use a real IFL out of the pool when it dispatches the guest. The guest could be dispatched on any available IFL. If you SET CPUAFFINITY OFF for the user (default is ON), all of the virtual CPUs will be dispatched on the primary CPU type (CP's for a z/VM mode LPAR). And Ray is correct - in a z/VM mode LPAR you need COMMAND SET VCONFIG MODE LINUX first. Look at the table in the DEFINE CPU command. (VCONFIG MODE ESA/390 is the default for non-Linux-only LPARs.) The relationship between the LPAR *mode*, as defined in the image profile (ESA/390, Linux, z/VM), and the valid primary and secondary CPU types is part of the machine architecture and is important to understand. It can seem a little strange until you realize that the purpose of this part of the architecture is to ensure that an LPAR's CPU configuration (a) is useful, (b) avoids abends, and (c) ensures workloads run on the CPUs they are licensed for. The SET VCONFIG command simulates the LPAR configuration mode and so the virtual CPU configuration is dictated. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Thank you for the clarifications. The VM LPAR in question is also running a z/OS guest hence the need to allocate the real CP's. From the HMC profile perspective, all the engines are shared among all the LPAR's. Re John S.'s question, we used the VM performance toolkit to observe a WAS/Linux workload and could see the work only dispatching on the CP's. I will report back when we get more info. Thank you all for the assistance. Edward Long --- On Thu, 7/22/10, Alan Altmark alan_altm...@us.ibm.com wrote: From: Alan Altmark alan_altm...@us.ibm.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Thursday, July 22, 2010, 10:15 AM On Wednesday, 07/21/2010 at 05:20 EDT, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). No. A z/VM *mode* LPAR on a z10 or zEnterprise has separate pools of CPs, IFLs, ICFs, zIIPs, and zAAPs at its disposal, depending on what's in the LPAR activation profile. By placing the IFL keyword on DEFINE CPU, you tell CP to use a real IFL out of the pool when it dispatches the guest. The guest could be dispatched on any available IFL. If you SET CPUAFFINITY OFF for the user (default is ON), all of the virtual CPUs will be dispatched on the primary CPU type (CP's for a z/VM mode LPAR). And Ray is correct - in a z/VM mode LPAR you need COMMAND SET VCONFIG MODE LINUX first. Look at the table in the DEFINE CPU command. (VCONFIG MODE ESA/390 is the default for non-Linux-only LPARs.) The relationship between the LPAR *mode*, as defined in the image profile (ESA/390, Linux, z/VM), and the valid primary and secondary CPU types is part of the machine architecture and is important to understand. It can seem a little strange until you realize that the purpose of this part of the architecture is to ensure that an LPAR's CPU configuration (a) is useful, (b) avoids abends, and (c) ensures workloads run on the CPUs they are licensed for. The SET VCONFIG command simulates the LPAR configuration mode and so the virtual CPU configuration is dictated. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On 7/21/2010 at 01:21 PM, Ed Long rdhm...@prodigy.net wrote: We have a z10 running VM 5.4 in LPAR #1. The box has 2 half speed CP's, 2 IFL's, and 2 ZAAP's. We want to modify a specific zLinux guest, call it zLinux1, to only run on the IFL's. So far, we can get it to see all 6 engines which is not good. Sorry if this is obvous to some, what would be the best practice for doing this? Can we do it all in the Directory? Yes. Can we do the configuration in such a way that it survives reboots and vm IPL's? Yes. In the USER DIRECT entry for the guest, add COMMAND DEFINE CPU 00 IFL If the Linux system is not consuming more than ~ 80% of a real CPU, it should only have one virtual CPU defined. If it really needs more than that, then add another COMMAND DEFINE CPU xx IFL statement for each one. For this to take effect, you'll need to shutdown the Linux guest and log it off. You could issue the #CP DEFINE CPU 00 IFL command instead, but make sure your Linux guest is all the way down, as it will cause a virtual machine system reset and clear. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). Edward Long --- On Wed, 7/21/10, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Wednesday, July 21, 2010, 5:02 PM On 7/21/2010 at 01:21 PM, Ed Long rdhm...@prodigy.net wrote: We have a z10 running VM 5.4 in LPAR #1. The box has 2 half speed CP's, 2 IFL's, and 2 ZAAP's. We want to modify a specific zLinux guest, call it zLinux1, to only run on the IFL's. So far, we can get it to see all 6 engines which is not good. Sorry if this is obvous to some, what would be the best practice for doing this? Can we do it all in the Directory? Yes. Can we do the configuration in such a way that it survives reboots and vm IPL's? Yes. In the USER DIRECT entry for the guest, add COMMAND DEFINE CPU 00 IFL If the Linux system is not consuming more than ~ 80% of a real CPU, it should only have one virtual CPU defined. If it really needs more than that, then add another COMMAND DEFINE CPU xx IFL statement for each one. For this to take effect, you'll need to shutdown the Linux guest and log it off. You could issue the #CP DEFINE CPU 00 IFL command instead, but make sure your Linux guest is all the way down, as it will cause a virtual machine system reset and clear. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IFL's, VM, and Linux
On 7/21/2010 at 05:16 PM, Ed Long rdhm...@prodigy.net wrote: Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? No. This is referring to the virtual CPUs that the guest will see, not the real hardware. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
