All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Wei, Gang" <gang.wei@intel.com>, Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Yu, Ke" <ke.yu@intel.com>
Subject: Re: [PATCH]ACPI: re-enable mwait for xen cpuidle
Date: Fri, 02 Apr 2010 15:27:40 +0100	[thread overview]
Message-ID: <C7DBBD6C.F83A%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E6467867A6B05E4FA831B7DF29925F5C40E67A6A@shzsmsx502.ccr.corp.intel.com>

It also has wider impact, including questionable effect on existing dom0
kernels which have never been tested with MONITOR/MWAIT present in
virtualised CPUID. I'm not sure about making this change even in current
xen-unstable (but not dead against it), and there's no chance for 4.0 and
3.4 branches.

 -- Keir

On 02/04/2010 14:41, "Wei, Gang" <gang.wei@intel.com> wrote:

> The 3rd choice: don't clear MWAIT feature in xen. This should be the best
> choice.
> 
> Jimmy
> 
> X86: re-enable mwait for xen cpuidle
> 
> Xen hypervisor doesn't export mwait feature to dom0, but latest Linux kernel
> start to check this feature while initializing _PDC object. Pass the MWAIT
> feature to dom0 to let dom0 got & pass to xen correct C state info.
> 
> Signed-off-by: Wei Gang <gang.wei@intel.com>
> 
> diff -r 537451477469 xen/arch/x86/traps.c
> --- a/xen/arch/x86/traps.c Thu Apr 01 09:55:27 2010 +0100
> +++ b/xen/arch/x86/traps.c Sat Apr 03 05:26:53 2010 +0800
> @@ -776,7 +776,6 @@ static void pv_cpuid(struct cpu_user_reg
>          __clear_bit(X86_FEATURE_PBE, &d);
>  
>          __clear_bit(X86_FEATURE_DTES64 % 32, &c);
> -        __clear_bit(X86_FEATURE_MWAIT % 32, &c);
>          __clear_bit(X86_FEATURE_DSCPL % 32, &c);
>          __clear_bit(X86_FEATURE_VMXE % 32, &c);
>          __clear_bit(X86_FEATURE_SMXE % 32, &c);
> @@ -814,7 +813,6 @@ static void pv_cpuid(struct cpu_user_reg
>          __clear_bit(X86_FEATURE_SKINIT % 32, &c);
>          __clear_bit(X86_FEATURE_WDT % 32, &c);
>          break;
> -    case 5: /* MONITOR/MWAIT */
>      case 0xa: /* Architectural Performance Monitor Features */
>      case 0x8000000a: /* SVM revision and features */
>      case 0x8000001b: /* Instruction Based Sampling */

  reply	other threads:[~2010-04-02 14:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02  2:38 [PATCH]ACPI: re-enable mwait for xen cpuidle Wei, Gang
2010-04-02  5:40 ` Jeremy Fitzhardinge
2010-04-02  6:32   ` Wei, Gang
2010-04-02  9:34     ` Wei, Gang
2010-04-02 13:41       ` Wei, Gang
2010-04-02 14:27         ` Keir Fraser [this message]
2010-04-02 14:46           ` Keir Fraser
2010-04-02 15:18             ` Wei, Gang
2010-04-02 16:27       ` Wei, Gang
2010-04-02 18:33         ` Jeremy Fitzhardinge
2010-04-03 14:07           ` Wei, Gang
2010-04-05 18:30             ` Jeremy Fitzhardinge
2010-04-06  1:46               ` Wei, Gang

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=C7DBBD6C.F83A%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=gang.wei@intel.com \
    --cc=jeremy@goop.org \
    --cc=ke.yu@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.