From: John Weekes <lists.xen@nuclearfallout.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: mark.langsdorf@amd.com,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
winston.l.wang@intel.com, gang.wei@intel.com
Subject: Re: Performance difference between Xen versions
Date: Mon, 02 May 2011 11:43:58 -0700 [thread overview]
Message-ID: <4DBEFB6E.4090201@nuclearfallout.net> (raw)
In-Reply-To: <20110502181222.GB7498@dumpdata.com>
On 5/2/2011 11:12 AM, Konrad Rzeszutek Wilk wrote:
> On Mon, May 02, 2011 at 10:52:45AM -0700, John Weekes wrote:
>> Or I am I just missing something entirely here?
> Oh? I think git commit a3ca5a20ec9d5c4917271021d49768961e7a8421
> Author: Yu Ke<ke.yu@intel.com>
> Date: Thu Apr 28 09:50:55 2011 -0400
>
> xen/acpi: add xen acpi processor driver
>
> Xen hypervisor need parsed acpi processor info for CPU Cx/Px power management,
> so this patch introduces xen acpi processor driver to parse the acpi info,
> and notify the hypervisor upon receiving the info.
>
> This patch has two components:
> - driver/acpi/processor_xen.c: implement the xen acpi processor driver
> - drivers/xen/acpi_processor.c: provide the interface to notify Xen hypervisor
>
> adds it in the 2.6.32 tree?
Thanks, Konrad.
It looks like the commit in question is actually this one, from March
2010:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=7529008534a694c5784dfb11aa46184e33adc227.
My search didn't find it because the files don't use the string
"px_pminfo" anywhere.
The important thing that I missed on my end was not having the ACPI
processor driver selected (for some reason). I had cpufreq and ACPI
enabled, but I needed that, as well.
-John
next prev parent reply other threads:[~2011-05-02 18:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 12:32 Performance difference between Xen versions Juergen Gross
2011-04-29 13:28 ` Keir Fraser
2011-04-29 13:35 ` Juergen Gross
2011-04-29 14:58 ` Keir Fraser
2011-04-29 16:10 ` Jan Beulich
2011-05-02 5:31 ` Juergen Gross
2011-05-02 6:41 ` Keir Fraser
2011-05-02 7:23 ` Jan Beulich
2011-05-02 8:00 ` Juergen Gross
2011-05-02 8:15 ` Jan Beulich
2011-05-02 8:23 ` Juergen Gross
2011-05-02 8:49 ` Keir Fraser
2011-05-03 3:06 ` Tian, Kevin
2011-05-06 13:49 ` Juergen Gross
2011-05-06 14:27 ` Jan Beulich
2011-05-11 6:08 ` Tian, Kevin
2011-05-11 6:23 ` Juergen Gross
2011-05-02 17:52 ` John Weekes
2011-05-02 18:12 ` Konrad Rzeszutek Wilk
2011-05-02 18:43 ` John Weekes [this message]
2011-05-02 19:16 ` John Weekes
2011-05-02 19:36 ` Konrad Rzeszutek Wilk
2011-05-02 19:54 ` John Weekes
2011-05-03 2:16 ` Tian, Kevin
2011-05-03 3:04 ` Tian, Kevin
2011-05-03 3:39 ` John Weekes
2011-05-03 7:23 ` Tian, Kevin
[not found] ` <4DBF13BB.3000309@nuclearfallout.net>
2011-05-03 7:23 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DBEFB6E.4090201@nuclearfallout.net \
--to=lists.xen@nuclearfallout.net \
--cc=gang.wei@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=mark.langsdorf@amd.com \
--cc=winston.l.wang@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.