mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Bernard Blackham <bernard@blackham.com.au>
Cc: mingo@elte.hu, ncunningham@linuxmail.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched-fix-scheduling-latencies-in-mttrc reenables interrupts
Date: Mon, 27 Dec 2004 01:36:53 -0800	[thread overview]
Message-ID: <20041227013653.67965d46.akpm@osdl.org> (raw)
In-Reply-To: <20041227062828.GE7415@blackham.com.au>

Bernard Blackham <bernard@blackham.com.au> wrote:
>
> The patch sched-fix-scheduling-latencies-in-mttr in recent -mm
>  kernels has the bad side-effect of re-enabling interrupts even if
>  they were disabled. This caused bugs in Software Suspend 2 which
>  reenabled MTRRs whilst interrupts were already disabled.

OK.

>  Attached is a replacement patch which uses spin_lock_irqsave instead
>  of spin_lock_irq.

>  +static unsigned long sal_flags;
>   
>   static void prepare_set(void)
>   {
>  @@ -240,11 +241,14 @@ static void prepare_set(void)
>   	/*  Note that this is not ideal, since the cache is only flushed/disabled
>   	   for this CPU while the MTRRs are changed, but changing this requires
>   	   more invasive changes to the way the kernel boots  */
>  -	spin_lock(&set_atomicity_lock);
>  +	/*
>  +	 * Since we are disabling the cache dont allow any interrupts - they
>  +	 * would run extremely slow and would only increase the pain:
>  +	 */
>  +	spin_lock_irqsave(&set_atomicity_lock, sal_flags);

Not OK.  That global `sal_flags' is not protected by the spinlock because
spin_lock_irqsave() saves the flags before taking the lock.

How about this?


diff -puN arch/i386/kernel/cpu/mtrr/generic.c~sched-fix-scheduling-latencies-in-mttrc-reenables-interrupts arch/i386/kernel/cpu/mtrr/generic.c
--- 25/arch/i386/kernel/cpu/mtrr/generic.c~sched-fix-scheduling-latencies-in-mttrc-reenables-interrupts	2004-12-27 01:31:41.718983736 -0800
+++ 25-akpm/arch/i386/kernel/cpu/mtrr/generic.c	2004-12-27 01:34:15.180654016 -0800
@@ -233,6 +233,13 @@ static unsigned long cr4 = 0;
 static u32 deftype_lo, deftype_hi;
 static spinlock_t set_atomicity_lock = SPIN_LOCK_UNLOCKED;
 
+/*
+ * Since we are disabling the cache don't allow any interrupts - they
+ * would run extremely slow and would only increase the pain.  The caller must
+ * ensure that local interrupts are disabled and are reenabled after post_set()
+ * has been called.
+ */
+
 static void prepare_set(void)
 {
 	unsigned long cr0;
@@ -240,11 +247,8 @@ static void prepare_set(void)
 	/*  Note that this is not ideal, since the cache is only flushed/disabled
 	   for this CPU while the MTRRs are changed, but changing this requires
 	   more invasive changes to the way the kernel boots  */
-	/*
-	 * Since we are disabling the cache dont allow any interrupts - they
-	 * would run extremely slow and would only increase the pain:
-	 */
-	spin_lock_irq(&set_atomicity_lock);
+
+	spin_lock(&set_atomicity_lock);
 
 	/*  Enter the no-fill (CD=1, NW=0) cache mode and flush caches. */
 	cr0 = read_cr0() | 0x40000000;	/* set CD flag */
@@ -281,19 +285,22 @@ static void post_set(void)
 	/*  Restore value of CR4  */
 	if ( cpu_has_pge )
 		write_cr4(cr4);
-	spin_unlock_irq(&set_atomicity_lock);
+	spin_unlock(&set_atomicity_lock);
 }
 
 static void generic_set_all(void)
 {
 	unsigned long mask, count;
+	unsigned long flags;
 
+	local_irq_save(flags);
 	prepare_set();
 
 	/* Actually set the state */
 	mask = set_mtrr_state(deftype_lo,deftype_hi);
 
 	post_set();
+	local_irq_restore(flags);
 
 	/*  Use the atomic bitops to update the global mask  */
 	for (count = 0; count < sizeof mask * 8; ++count) {
@@ -316,6 +323,9 @@ static void generic_set_mtrr(unsigned in
     [RETURNS] Nothing.
 */
 {
+	unsigned long flags;
+
+	local_irq_save(flags);
 	prepare_set();
 
 	if (size == 0) {
@@ -330,6 +340,7 @@ static void generic_set_mtrr(unsigned in
 	}
 
 	post_set();
+	local_irq_restore(flags);
 }
 
 int generic_validate_add_page(unsigned long base, unsigned long size, unsigned int type)
_


  reply	other threads:[~2004-12-27  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-27  6:28 Bernard Blackham
2004-12-27  9:36 ` Andrew Morton [this message]
2004-12-27 15:20   ` Bernard Blackham

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=20041227013653.67965d46.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bernard@blackham.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ncunningham@linuxmail.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

Powered by JetHome