From: Andi Kleen <ak@suse.de>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: john stultz <johnstul@us.ibm.com>,
caglar@pardus.org.tr, lkml <linux-kernel@vger.kernel.org>,
Zachary Amsden <zach@vmware.com>
Subject: Vmware problems was Re: [RFC] Avoid PIT SMP lockups
Date: Mon, 16 Oct 2006 18:22:48 +0200 [thread overview]
Message-ID: <200610161822.48500.ak@suse.de> (raw)
In-Reply-To: <4533AE82.6010502@suse.de>
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
next prev parent reply other threads:[~2006-10-16 16:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 21:38 [RFC] Avoid PIT SMP lockups john stultz
2006-10-07 15:50 ` S.Çağlar Onur
2006-10-10 9:11 ` S.Çağlar Onur
2006-10-10 18:27 ` john stultz
2006-10-11 10:49 ` S.Çağlar Onur
2006-10-11 17:59 ` john stultz
2006-10-11 18:37 ` S.Çağlar Onur
2006-10-11 18:43 ` john stultz
2006-10-11 19:09 ` S.Çağlar Onur
2006-10-11 19:26 ` john stultz
2006-10-11 19:31 ` S.Çağlar Onur
2006-10-12 7:28 ` Gerd Hoffmann
2006-10-12 7:45 ` S.Çağlar Onur
2006-10-16 22:17 ` Zachary Amsden
2006-10-16 22:21 ` S.Çağlar Onur
2006-10-17 12:05 ` S.Çağlar Onur
2006-10-17 12:16 ` Andi Kleen
2006-10-19 8:00 ` [PATCH] Fix potential interrupts during alternative patching [was Re: [RFC] Avoid PIT SMP lockups] Zachary Amsden
2006-10-19 8:49 ` Jeremy Fitzhardinge
2006-10-19 9:00 ` Zachary Amsden
2006-10-20 10:36 ` S.Çağlar Onur
2006-10-20 5:25 ` Greg KH
2006-10-16 22:40 ` [RFC] Avoid PIT SMP lockups Andi Kleen
2006-10-16 23:25 ` Zachary Amsden
2006-10-16 16:08 ` Gerd Hoffmann
2006-10-16 16:22 ` Andi Kleen [this message]
2006-10-16 22:16 ` Vmware problems was " Petr Vandrovec
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=200610161822.48500.ak@suse.de \
--to=ak@suse.de \
--cc=caglar@pardus.org.tr \
--cc=johnstul@us.ibm.com \
--cc=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.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