public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Loic Prylli <loic@myri.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] MTRR: Fix race causing set_mtrr to go into infinite loop
Date: Mon, 25 Jun 2007 18:05:17 -0400	[thread overview]
Message-ID: <46803C1D.2040009@redhat.com> (raw)
In-Reply-To: <468035BC.9080008@myri.com>

On 06/25/2007 05:38 PM, Loic Prylli wrote:

[cc: Andi]

> Processors synchronization in set_mtrr requires the .gate field
> to be set after .count field is properly initialized. Without an explicit
> barrier, the compiler was reordering those memory stores. That was sometimes
> causing a processor (in ipi_handler) to see the .gate change and
> decrement .count before the latter is set by set_mtrr() (which
> then hangs in a infinite loop with irqs disabled).
> 
> Signed-off-by: Loic Prylli <loic@myri.com>
> ---
>  arch/i386/kernel/cpu/mtrr/main.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/i386/kernel/cpu/mtrr/main.c b/arch/i386/kernel/cpu/mtrr/main.c
> index 55b0051..75dc6d5 100644
> --- a/arch/i386/kernel/cpu/mtrr/main.c
> +++ b/arch/i386/kernel/cpu/mtrr/main.c
> @@ -229,6 +229,8 @@ static void set_mtrr(unsigned int reg, unsigned long base,
>  	data.smp_size = size;
>  	data.smp_type = type;
>  	atomic_set(&data.count, num_booting_cpus() - 1);
> +	/* make sure data.count is visible before unleashing other CPUs */
> +	smp_wmb();
>  	atomic_set(&data.gate,0);
>  
>  	/*  Start the ball rolling on other CPUs  */
> @@ -242,6 +244,7 @@ static void set_mtrr(unsigned int reg, unsigned long base,
>  
>  	/* ok, reset count and toggle gate */
>  	atomic_set(&data.count, num_booting_cpus() - 1);
> +	smp_wmb();
>  	atomic_set(&data.gate,1);
>  
>  	/* do our MTRR business */
> @@ -260,6 +263,7 @@ static void set_mtrr(unsigned int reg, unsigned long base,
>  		cpu_relax();
>  
>  	atomic_set(&data.count, num_booting_cpus() - 1);
> +	smp_wmb();
>  	atomic_set(&data.gate,0);
>  
>  	/*

  reply	other threads:[~2007-06-25 22:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 21:38 [PATCH] MTRR: Fix race causing set_mtrr to go into infinite loop Loic Prylli
2007-06-25 22:05 ` Chuck Ebbert [this message]
2007-06-25 22:34   ` Andi Kleen
2007-06-26  1:40     ` Loic Prylli
2007-06-28 19:52     ` Chuck Ebbert

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=46803C1D.2040009@redhat.com \
    --to=cebbert@redhat.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic@myri.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox