* [Qemu-devel] qemu 0.5.1 emulation bug?
@ 2004-01-24 14:09 Rusty Russell
2004-01-24 16:30 ` [Qemu-devel] " Fabrice Bellard
2004-01-24 17:45 ` [Qemu-devel] " Herbert Poetzl
0 siblings, 2 replies; 4+ messages in thread
From: Rusty Russell @ 2004-01-24 14:09 UTC (permalink / raw)
To: Fabrice Bellard; +Cc: qemu-devel
Just spent two hours chasing down why recent 2.6.2-rc1 kernels don't
boot.
It turns out that find_next_bit() returns 0 under "qemu-fast" and
"qemu" where it returns 32 under "qemu-i386" and native x86.
Bedtime for me, but here's the offending code:
/**
* find_first_bit - find the first set bit in a memory region
* @addr: The address to start the search at
* @size: The maximum size to search
*
* Returns the bit-number of the first set bit, not the number of the byte
* containing a bit.
*/
static __inline__ int xfind_first_bit(const unsigned long *addr, unsigned size)
{
int d0, d1;
int res;
/* This looks at memory. Mark it volatile to tell gcc not to move it around */
__asm__ __volatile__(
"xorl %%eax,%%eax\n\t"
"repe; scasl\n\t"
"jz 1f\n\t"
"leal -4(%%edi),%%edi\n\t"
"bsfl (%%edi),%%eax\n"
"1:\tsubl %%ebx,%%edi\n\t"
"shll $3,%%edi\n\t"
"addl %%edi,%%eax"
:"=a" (res), "=&c" (d0), "=&D" (d1)
:"1" ((size + 31) >> 5), "2" (addr), "b" (addr));
return res;
}
/**
* find_next_bit - find the first set bit in a memory region
* @addr: The address to base the search on
* @offset: The bitnumber to start searching at
* @size: The maximum size to search
*/
static __inline__ int xfind_next_bit(const unsigned long *addr, int size, int offset)
{
const unsigned long *p = addr + (offset >> 5);
int set = 0, bit = offset & 31, res;
if (bit) {
/*
* Look for nonzero in the first 32 bits:
*/
__asm__("bsfl %1,%0\n\t"
"jne 1f\n\t"
"movl $32, %0\n"
"1:"
: "=r" (set)
: "r" (*p >> bit));
if (set < (32 - bit))
return set + offset;
set = 32 - bit;
p++;
}
/*
* No set bit yet, search remaining full words for a bit
*/
res = xfind_first_bit (p, size - 32 * (p - addr));
return (offset + set + res);
}
int main()
{
unsigned long map = 1;
printf("find_next_bit of %lu = %i\n",
map, xfind_next_bit(&map, 32, 1));
return 0;
}
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Qemu-devel] Re: qemu 0.5.1 emulation bug?
2004-01-24 14:09 [Qemu-devel] qemu 0.5.1 emulation bug? Rusty Russell
@ 2004-01-24 16:30 ` Fabrice Bellard
2004-01-24 17:45 ` [Qemu-devel] " Herbert Poetzl
1 sibling, 0 replies; 4+ messages in thread
From: Fabrice Bellard @ 2004-01-24 16:30 UTC (permalink / raw)
To: qemu-devel
Thanx for the report. It should work now (eflags optimisation bug with
string operations).
Fabrice.
Rusty Russell wrote:
> Just spent two hours chasing down why recent 2.6.2-rc1 kernels don't
> boot.
>
> It turns out that find_next_bit() returns 0 under "qemu-fast" and
> "qemu" where it returns 32 under "qemu-i386" and native x86.
>
> Bedtime for me, but here's the offending code:
>
> /**
> * find_first_bit - find the first set bit in a memory region
> * @addr: The address to start the search at
> * @size: The maximum size to search
> *
> * Returns the bit-number of the first set bit, not the number of the byte
> * containing a bit.
> */
> static __inline__ int xfind_first_bit(const unsigned long *addr, unsigned size)
> {
> int d0, d1;
> int res;
>
> /* This looks at memory. Mark it volatile to tell gcc not to move it around */
> __asm__ __volatile__(
> "xorl %%eax,%%eax\n\t"
> "repe; scasl\n\t"
> "jz 1f\n\t"
> "leal -4(%%edi),%%edi\n\t"
> "bsfl (%%edi),%%eax\n"
> "1:\tsubl %%ebx,%%edi\n\t"
> "shll $3,%%edi\n\t"
> "addl %%edi,%%eax"
> :"=a" (res), "=&c" (d0), "=&D" (d1)
> :"1" ((size + 31) >> 5), "2" (addr), "b" (addr));
> return res;
> }
>
> /**
> * find_next_bit - find the first set bit in a memory region
> * @addr: The address to base the search on
> * @offset: The bitnumber to start searching at
> * @size: The maximum size to search
> */
> static __inline__ int xfind_next_bit(const unsigned long *addr, int size, int offset)
> {
> const unsigned long *p = addr + (offset >> 5);
> int set = 0, bit = offset & 31, res;
>
> if (bit) {
> /*
> * Look for nonzero in the first 32 bits:
> */
> __asm__("bsfl %1,%0\n\t"
> "jne 1f\n\t"
> "movl $32, %0\n"
> "1:"
> : "=r" (set)
> : "r" (*p >> bit));
> if (set < (32 - bit))
> return set + offset;
> set = 32 - bit;
> p++;
> }
> /*
> * No set bit yet, search remaining full words for a bit
> */
> res = xfind_first_bit (p, size - 32 * (p - addr));
> return (offset + set + res);
> }
>
> int main()
> {
> unsigned long map = 1;
>
> printf("find_next_bit of %lu = %i\n",
> map, xfind_next_bit(&map, 32, 1));
> return 0;
> }
>
>
> --
> Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] qemu 0.5.1 emulation bug?
2004-01-24 14:09 [Qemu-devel] qemu 0.5.1 emulation bug? Rusty Russell
2004-01-24 16:30 ` [Qemu-devel] " Fabrice Bellard
@ 2004-01-24 17:45 ` Herbert Poetzl
2004-01-25 2:15 ` Rusty Russell
1 sibling, 1 reply; 4+ messages in thread
From: Herbert Poetzl @ 2004-01-24 17:45 UTC (permalink / raw)
To: Rusty Russell; +Cc: qemu-devel
On Sun, Jan 25, 2004 at 01:09:52AM +1100, Rusty Russell wrote:
> Just spent two hours chasing down why recent 2.6.2-rc1 kernels don't
> boot.
hum, interesting, 2.6.2-rc1 is booting here, with
the 'to be tested' cvs version ... (5.2 rc)
best,
Herbert
> It turns out that find_next_bit() returns 0 under "qemu-fast" and
> "qemu" where it returns 32 under "qemu-i386" and native x86.
>
> Bedtime for me, but here's the offending code:
>
> /**
> * find_first_bit - find the first set bit in a memory region
> * @addr: The address to start the search at
> * @size: The maximum size to search
> *
> * Returns the bit-number of the first set bit, not the number of the byte
> * containing a bit.
> */
> static __inline__ int xfind_first_bit(const unsigned long *addr, unsigned size)
> {
> int d0, d1;
> int res;
>
> /* This looks at memory. Mark it volatile to tell gcc not to move it around */
> __asm__ __volatile__(
> "xorl %%eax,%%eax\n\t"
> "repe; scasl\n\t"
> "jz 1f\n\t"
> "leal -4(%%edi),%%edi\n\t"
> "bsfl (%%edi),%%eax\n"
> "1:\tsubl %%ebx,%%edi\n\t"
> "shll $3,%%edi\n\t"
> "addl %%edi,%%eax"
> :"=a" (res), "=&c" (d0), "=&D" (d1)
> :"1" ((size + 31) >> 5), "2" (addr), "b" (addr));
> return res;
> }
>
> /**
> * find_next_bit - find the first set bit in a memory region
> * @addr: The address to base the search on
> * @offset: The bitnumber to start searching at
> * @size: The maximum size to search
> */
> static __inline__ int xfind_next_bit(const unsigned long *addr, int size, int offset)
> {
> const unsigned long *p = addr + (offset >> 5);
> int set = 0, bit = offset & 31, res;
>
> if (bit) {
> /*
> * Look for nonzero in the first 32 bits:
> */
> __asm__("bsfl %1,%0\n\t"
> "jne 1f\n\t"
> "movl $32, %0\n"
> "1:"
> : "=r" (set)
> : "r" (*p >> bit));
> if (set < (32 - bit))
> return set + offset;
> set = 32 - bit;
> p++;
> }
> /*
> * No set bit yet, search remaining full words for a bit
> */
> res = xfind_first_bit (p, size - 32 * (p - addr));
> return (offset + set + res);
> }
>
> int main()
> {
> unsigned long map = 1;
>
> printf("find_next_bit of %lu = %i\n",
> map, xfind_next_bit(&map, 32, 1));
> return 0;
> }
>
>
> --
> Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] qemu 0.5.1 emulation bug?
2004-01-24 17:45 ` [Qemu-devel] " Herbert Poetzl
@ 2004-01-25 2:15 ` Rusty Russell
0 siblings, 0 replies; 4+ messages in thread
From: Rusty Russell @ 2004-01-25 2:15 UTC (permalink / raw)
To: Herbert Poetzl; +Cc: qemu-devel
In message <20040124174516.GA11039@MAIL.13thfloor.at> you write:
> On Sun, Jan 25, 2004 at 01:09:52AM +1100, Rusty Russell wrote:
> > Just spent two hours chasing down why recent 2.6.2-rc1 kernels don't
> > boot.
>
> hum, interesting, 2.6.2-rc1 is booting here, with
> the 'to be tested' cvs version ... (5.2 rc)
That code isn't used to boot unless you're SMP: nr_running() is
calculated to set up the proc subsystem, which uses for_each_cpu,
which uses find_next_bit().
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-01-25 2:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-24 14:09 [Qemu-devel] qemu 0.5.1 emulation bug? Rusty Russell
2004-01-24 16:30 ` [Qemu-devel] " Fabrice Bellard
2004-01-24 17:45 ` [Qemu-devel] " Herbert Poetzl
2004-01-25 2:15 ` Rusty Russell
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).