I have dual core Opteron 275 with AMD PowerNow! and frequency scaling. This is how I boot xen: kernel$ /boot/$ISADIR/xen.gz console=vga cpufreq=xen dom0_mem=3072M dom0_vcpus_pin=false watchdog=false but when I run xenpm this is what I get: # xenpm Xen cpuidle is not enabled! [CPU0] failed to get max P-state [CPU1] failed to get max P-state [CPU2] failed to get max P-state [CPU3] failed to get max P-state Is power management supported (build 127)? Why am I getting this error? Thank you in advance. -- This message posted from opensolaris.org
Jensen Lee wrote:> I have dual core Opteron 275 with AMD PowerNow! and frequency scaling. > > This is how I boot xen: > > kernel$ /boot/$ISADIR/xen.gz console=vga cpufreq=xen dom0_mem=3072M dom0_vcpus_pin=false watchdog=false > > but when I run xenpm this is what I get: > # xenpm > Xen cpuidle is not enabled! > [CPU0] failed to get max P-state > [CPU1] failed to get max P-state > [CPU2] failed to get max P-state > [CPU3] failed to get max P-state > > Is power management supported (build 127)? Why am I getting this error? > > Thank you in advance. >It could be that the hypercalls needed by xenpm aren''t properly handled by the dom0 kernel interface. The power management code isn''t something we have been using on our dom0 so far. I''ll have a look at it. Thanks for reporting this, - Frank
> It could be that the hypercalls needed by xenpm aren''t properly > handled by the dom0 kernel interface. The power management code isn''t > something we have been using on our dom0 so far. I''ll have a look at it.I checked, and there are indeed some power management hypercalls that aren''t handled. These are easy enough to implement, but the PM interface also needs some hooks in the dom0 ACPI code to inform Xen about CPU PM capabilities. Since we don''t have those hooks, adding support for the hypercalls isn''t going to help. I''ll have a peek at what it takes to support the PM interface, but I wouldn''t expect support for it soon, since it''s probably not a priority. - Frank
> > It could be that the hypercalls needed by xenpm > aren''t properly > handled by the dom0 kernel interface. The power > management code isn''t > something we have been using on our dom0 so far. > I''ll have a look at it. > checked, and there are indeed some power management > hypercalls that > ren''t handled. > > These are easy enough to implement, but the PM > interface also needs some > hooks in the dom0 ACPI code to inform Xen about CPU > PM capabilities. > Since we don''t have those hooks, adding support for > the hypercalls isn''t > going to help. > > I''ll have a peek at what it takes to support the PM > interface, but I > wouldn''t expect support for it soon, since it''s > probably not a priority. > > - Frank > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgFrank, thank you for looking into this. With regard to priorities, I am afraid I disagree. I can see Xen is working fairly stable, whilst however tons of carbon dioxide are sent into the atmosphere every hour without need, because there are thousands of workstations and servers running idle and using power that they should not to. I see that you are working for Sun, and assuming you live in the US, this is against EPA regulations. Assuming that you live on this planet and that you do take seriously your responsibilities towards the pollution of our atmosphere, your responsibilities are even greater when you have the power to prioritize on a tool that can potentially have a great impact on the quality of everyone''s life. Just to put the impact into perspective, an average dual core Opteron utilizes 95Watts hour, but through power management it can save up to 50Watts per hour. an average server or high end workstation have two processors. 50W hour x 2 = 100W hour x 24 = 2400W or 2.4 Kilowatts In 30 days such server or workstation will consume 72 Kilowatts more than what it should have. OpenSolaris and Solaris are distributed to a large user base. For 10.000 installations this would mean 24 Megawatts every month. 100.000 installations mean 240 Megawatts and tons of carbon dioxide into the atmosphere that could have been saved. Now do you still think that handling power management is not a priority? -- This message posted from opensolaris.org
It seems harsh to harass Frank for explaining his understanding of his employer''s priorities. If you believe that this is a particularly important area, please feel free to post some patches that address the issues. We would be happy to include them if they work properly. dme. -- David Edmondson, Sun Microsystems, http://dme.org
> It seems harsh to harass Frank for explaining his > understanding of his > employer''s priorities.It seems to me harsh to to deem as harassment an argument towards a just cause. Nothing personal towards Frank in any case who I believe dealt with the matter as best as he could. And, as I suggested, if not under Frank''s control this matter should be escalated.> If you believe that this is a particularly important > area, please feel > free to post some patches that address the issues. WeIf I could I would, but I am no Xen code expert. And you could have spared this sarcastic challenge. -- This message posted from opensolaris.org
I have now run simple comparison tests on a dual Opteron 275 system (dual core with frequency scaling AMD PowerNow!) to measure the actual impact: 1) OpenSolaris build 128: idle 200-220 Watts, browsing the Internet with firefox 200-220Watts 2) Fedora 12: idle 75Watts, Browsing the Internet 110-120Watts, compiling the kernel 170-220Watts -- This message posted from opensolaris.org
Jensen Lee wrote:> I have now run simple comparison tests on a dual Opteron 275 system (dual core with frequency scaling AMD PowerNow!) to measure the actual impact: > > 1) OpenSolaris build 128: idle 200-220 Watts, browsing the Internet with firefox 200-220Watts > > 2) Fedora 12: idle 75Watts, Browsing the Internet 110-120Watts, compiling the kernel 170-220Watts >I assume you mean "OpenSolaris dom0" and "Fedora 12 dom0", since OpenSolaris most definitely has power management. Anyway, I implemented the needed support for Xen power management. The bug id is 6909899. You can see the changes here: http://cr.opensolaris.org/~fvdl/xenpm-xvm/ http://cr.opensolaris.org/~fvdl/xenpm-on/ I can''t make any promises about the integration date. The holidays are coming up, OpenSolaris is approaching a new release which means stricter rules on what can be integrated. And then, obviously, changes will come to Sun early next year with the takeover, of which I don''t know the details (and couldn''t tell you if I did). But, hopefully it will make it in soon. - Frank
Frank, Many thanks for taking care of this. Really, really appreciated.> Frank wrote: > I assume you mean "OpenSolaris dom0" and "Fedora 12 dom0", since > OpenSolaris most definitely has power management.To clarify test (1) refers OpenSolaris booted both as dom0 and plain (without Xen) There is no difference in power consumption because OpenSolaris plain kernel does not support Opteron families 15 and below power management. In this configuration, With OpenSolaris dom0 I had Fedora 12 also as domU. Test (2) refers to Fedora 12 with plain kernel boot as FC12''s kernel does not support dom0. -- This message posted from opensolaris.org
On Dec 12, 2009, at 8:11 PM, Frank Van Der Linden wrote:> > Anyway, I implemented the needed support for Xen power management. The bug id is 6909899. You can see the changes here: > > http://cr.opensolaris.org/~fvdl/xenpm-xvm/ > http://cr.opensolaris.org/~fvdl/xenpm-on/ > > I can''t make any promises about the integration date. The holidays are coming up, OpenSolaris is approaching a new release which means stricter rules on what can be integrated. And then, obviously, changes will come to Sun early next year with the takeover, of which I don''t know the details (and couldn''t tell you if I did). > > But, hopefully it will make it in soon.Can we hope for this to integrate soon now that the gates are open? ;) Regards Henrik http://sparcv9.blogspot.com