All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Wei, Gang" <gang.wei@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	"Yu, Ke" <ke.yu@intel.com>
Subject: Re: [PATCH]ACPI: re-enable mwait for xen cpuidle
Date: Thu, 01 Apr 2010 22:40:35 -0700	[thread overview]
Message-ID: <4BB58353.5000008@goop.org> (raw)
In-Reply-To: <E6467867A6B05E4FA831B7DF29925F5C40E677DD@shzsmsx502.ccr.corp.intel.com>

On 04/01/2010 07:38 PM, Wei, Gang wrote:
> I suggest including this patch in Xen 4.0 release. It is quite straightforward, and make sure the better and widely equipped cpu idle entry method MWAIT is used by xen if available.
>
> BTW, can we consider re-open MWAIT freature for dom0 in xen hypervisor? We can discuss it post 4.0.
>
> Jimmy
>
> ACPI: 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. Bypass such check in pv-ops case to re-enable mwait for xen cpuidle.
>    

Why not just set or clear the MWAIT feature flag in xen_cpuid?

     J

> Signed-off-by: Wei Gang<gang.wei@intel.com>
> Signed-off-by: Yu Ke<ke.yu@intel.com>
>
> diff --git a/arch/x86/kernel/acpi/processor.c b/arch/x86/kernel/acpi/processor.c
> index 8c9526d..d88866c 100644
> --- a/arch/x86/kernel/acpi/processor.c
> +++ b/arch/x86/kernel/acpi/processor.c
> @@ -60,7 +60,7 @@ static void init_intel_pdc(struct acpi_processor *pr, struct cpuinfo_x86 *c)
>   	/*
>   	 * If mwait/monitor is unsupported, C2/C3_FFH will be disabled
>   	 */
> -	if (!cpu_has(c, X86_FEATURE_MWAIT))
> +	if (!cpu_has(c, X86_FEATURE_MWAIT)&&  !xen_initial_domain())
>   		buf[2]&= ~(ACPI_PDC_C_C2C3_FFH);
>
>   	obj->type = ACPI_TYPE_BUFFER;
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index 22baf4c..0a81637 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -419,7 +419,8 @@ static int acpi_processor_get_power_info_cst(struct acpi_processor *pr)
>   				cx.entry_method = ACPI_CSTATE_HALT;
>   				snprintf(cx.desc, ACPI_CX_DESC_LEN, "ACPI HLT");
>   			} else {
> -				continue;
> +				if (!xen_initial_domain())
> +					continue;
>   			}
>   			if (cx.type == ACPI_STATE_C1&&
>   					(idle_halt || idle_nomwait)) {
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    

  reply	other threads:[~2010-04-02  5:40 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 [this message]
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
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=4BB58353.5000008@goop.org \
    --to=jeremy@goop.org \
    --cc=gang.wei@intel.com \
    --cc=ke.yu@intel.com \
    --cc=keir.fraser@eu.citrix.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.