xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/cpuidle: restrict scope of mwait_ptr in acpi_dead_idle()
Date: Tue, 06 Mar 2012 15:01:09 +0000	[thread overview]
Message-ID: <CB7BD735.3AE90%keir@xen.org> (raw)
In-Reply-To: <4F56341A0200007800076ACC@nat28.tlf.novell.com>

On 06/03/2012 14:58, "Jan Beulich" <JBeulich@suse.com> wrote:

> ... just to make sure it doesn't get used improperly (resulting from
> the discussion around what became c/s 24968:8964c223836c).
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Keir Fraser <keir@xen.org>

> --- a/xen/arch/x86/acpi/cpu_idle.c
> +++ b/xen/arch/x86/acpi/cpu_idle.c
> @@ -565,7 +565,6 @@ static void acpi_dead_idle(void)
>  {
>      struct acpi_processor_power *power;
>      struct acpi_processor_cx *cx;
> -    void *mwait_ptr;
>  
>      if ( (power = processor_powers[smp_processor_id()]) == NULL )
>          goto default_halt;
> @@ -573,10 +572,10 @@ static void acpi_dead_idle(void)
>      if ( (cx = &power->states[power->count-1]) == NULL )
>          goto default_halt;
>  
> -    mwait_ptr = (void *)&mwait_wakeup(smp_processor_id());
> -
>      if ( cx->entry_method == ACPI_CSTATE_EM_FFH )
>      {
> +        void *mwait_ptr = &mwait_wakeup(smp_processor_id());
> +
>          /*
>           * Cache must be flushed as the last operation before sleeping.
>           * Otherwise, CPU may still hold dirty data, breaking cache
> coherency,
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2012-03-06 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 14:58 [PATCH] x86/cpuidle: restrict scope of mwait_ptr in acpi_dead_idle() Jan Beulich
2012-03-06 15:01 ` Keir Fraser [this message]

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=CB7BD735.3AE90%keir@xen.org \
    --to=keir@xen.org \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).