On Monday 16 October 2006 18:08, Gerd Hoffmann wrote:
> john stultz wrote:
> > Hey Gerd,
> > Looks like the smp replacements code in 2.6.18 is breaking with vmware.
> > I'm guessing we're taking an interrupt while apply_replacements is
> > running. Any ideas?
>
> It's not the smp alternatives code, its the one for processor-specific
> instructions. The eip offset for alternative_instructions() in the
> trace suggests it is the first call to apply_replacements. The second
> one is the one for the smp alternatives (which doesn't do anything btw
> as we patch away the lock prefixes only).
I would have expected that they trap those writes and invalidate the cache.
Even qemu and valgrind do that fine.
Perhaps Zach has some clue or can refer to someone who has.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
