Re: Please revert 709f744 (x86: bitops asm constraint fixes)
From: Simon Holm Thøgersen
Date: Tue May 06 2008 - 08:33:50 EST
tir, 06 05 2008 kl. 14:01 +0200, skrev Ingo Molnar:
> * Simon Holm ThÃgersen <odie@xxxxxxxxx> wrote:
>
> > [CC'ing all that commented on the patch on LKML]
> >
> > 709f744 causes my computer to freeze during the start up of X and my
> > login manger (GDM). It gets to the point where it has shown the
> > default X mouse cursor logo (a big X / cross) and does not respond to
> > anything from that point on.
> >
> > This worked fine before 709f744, and it works fine with ï709f744
> > reverted on top of Linus' current tree (f74d505). The revert had
> > conflicts, as far as I can tell due to white space changes. The diff I
> > ended up with is below.
> >
> > It is 100% reproducible.
>
> thanks Simon for tracking this down.
>
> I've applied your revert (see the patch below), we'll do it unless the
> real bug is found and confirmed by you.
Thanks, I really only wanted to state that there was a bug somewhere,
but I was pretty tired of having used the whole day bisecting it down to
this change (took double the time because of something in the build
system apparently not rebuilding properly, leading to first a wrong
bisection and then extra compile time because of having to cautiously
make clean between each compile).
Anyway, if there's something I can do to provide further debug
information I'll be happy to help. Could there be a chance that
netconsole will catch something?
> What exact compiler version are you using to build the kernel?
gcc-4.2.3 (from Gentoo's portage tree). Should I try with the gcc-3.4.6
I've got lying around as well?
Also, I'm not sure how much havoc a broken video driver in user space
can wreck? It's not that I've changed anything in my userland for quite
some time, or that I'm not positive that this patch in the kernel makes
a difference, but I really don't know much about this.
>
> Jan, any ideas what's wrong with your commit?
>
> Ingo
Simon
>
> ------------->
> Subject: revert commit 709f744 ("x86: bitops asm constraint fixes")
> From: Simon Holm =?ISO-8859-1?Q?Th=F8gersen?= <odie@xxxxxxxxx>
> Date: Mon, 05 May 2008 15:45:28 +0200
>
> 709f744 causes my computer to freeze during the start up of X and my
> login manger (GDM). It gets to the point where it has shown the default
> X mouse cursor logo (a big X / cross) and does not respond to anything
> from that point on.
>
> This worked fine before 709f744, and it works fine with ï709f744
> reverted on top of Linus' current tree (f74d505). The revert had
> conflicts, as far as I can tell due to white space changes. The diff I
> ended up with is below.
>
> It is 100% reproducible.
>
> Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
> ---
> include/asm-x86/bitops.h | 37 +++++++++++++++++--------------------
> 1 file changed, 17 insertions(+), 20 deletions(-)
>
> Index: linux-x86.q/include/asm-x86/bitops.h
> ===================================================================
> --- linux-x86.q.orig/include/asm-x86/bitops.h
> +++ linux-x86.q/include/asm-x86/bitops.h
> @@ -23,13 +23,10 @@
> #if __GNUC__ < 4 || (__GNUC__ == 4 && __GNUC_MINOR__ < 1)
> /* Technically wrong, but this avoids compilation errors on some gcc
> versions. */
> -#define ADDR "=m" (*(volatile long *)addr)
> -#define BIT_ADDR "=m" (((volatile int *)addr)[nr >> 5])
> +#define ADDR "=m" (*(volatile long *) addr)
> #else
> #define ADDR "+m" (*(volatile long *) addr)
> -#define BIT_ADDR "+m" (((volatile int *)addr)[nr >> 5])
> #endif
> -#define BASE_ADDR "m" (*(volatile int *)addr)
>
> /**
> * set_bit - Atomically set a bit in memory
> @@ -77,7 +74,7 @@ static inline void __set_bit(int nr, vol
> */
> static inline void clear_bit(int nr, volatile void *addr)
> {
> - asm volatile(LOCK_PREFIX "btr %1,%2" : BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + asm volatile(LOCK_PREFIX "btr %1,%0" : ADDR : "Ir" (nr));
> }
>
> /*
> @@ -96,7 +93,7 @@ static inline void clear_bit_unlock(unsi
>
> static inline void __clear_bit(int nr, volatile void *addr)
> {
> - asm volatile("btr %1,%2" : BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + asm volatile("btr %1,%0" : ADDR : "Ir" (nr));
> }
>
> /*
> @@ -131,7 +128,7 @@ static inline void __clear_bit_unlock(un
> */
> static inline void __change_bit(int nr, volatile void *addr)
> {
> - asm volatile("btc %1,%2" : BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + asm volatile("btc %1,%0" : ADDR : "Ir" (nr));
> }
>
> /**
> @@ -145,7 +142,7 @@ static inline void __change_bit(int nr,
> */
> static inline void change_bit(int nr, volatile void *addr)
> {
> - asm volatile(LOCK_PREFIX "btc %1,%2" : BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + asm volatile(LOCK_PREFIX "btc %1,%0" : ADDR : "Ir" (nr));
> }
>
> /**
> @@ -191,9 +188,10 @@ static inline int __test_and_set_bit(int
> {
> int oldbit;
>
> - asm volatile("bts %2,%3\n\t"
> - "sbb %0,%0"
> - : "=r" (oldbit), BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + asm("bts %2,%1\n\t"
> + "sbb %0,%0"
> + : "=r" (oldbit), ADDR
> + : "Ir" (nr));
> return oldbit;
> }
>
> @@ -229,9 +227,10 @@ static inline int __test_and_clear_bit(i
> {
> int oldbit;
>
> - asm volatile("btr %2,%3\n\t"
> + asm volatile("btr %2,%1\n\t"
> "sbb %0,%0"
> - : "=r" (oldbit), BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + : "=r" (oldbit), ADDR
> + : "Ir" (nr));
> return oldbit;
> }
>
> @@ -240,9 +239,10 @@ static inline int __test_and_change_bit(
> {
> int oldbit;
>
> - asm volatile("btc %2,%3\n\t"
> + asm volatile("btc %2,%1\n\t"
> "sbb %0,%0"
> - : "=r" (oldbit), BIT_ADDR : "Ir" (nr), BASE_ADDR);
> + : "=r" (oldbit), ADDR
> + : "Ir" (nr) : "memory");
>
> return oldbit;
> }
> @@ -276,11 +276,10 @@ static inline int variable_test_bit(int
> {
> int oldbit;
>
> - asm volatile("bt %2,%3\n\t"
> + asm volatile("bt %2,%1\n\t"
> "sbb %0,%0"
> : "=r" (oldbit)
> - : "m" (((volatile const int *)addr)[nr >> 5]),
> - "Ir" (nr), BASE_ADDR);
> + : "m" (*(unsigned long *)addr), "Ir" (nr));
>
> return oldbit;
> }
> @@ -397,8 +396,6 @@ static inline int fls(int x)
> }
> #endif /* __KERNEL__ */
>
> -#undef BASE_ADDR
> -#undef BIT_ADDR
> #undef ADDR
>
> static inline void set_bit_string(unsigned long *bitmap,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/