From: Jamie Lokier <jamie@shareable.org>
To: Alexander Graf <agraf@suse.de>
Cc: Jakub Jermar <jakub@jermar.eu>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Atomicity of i386 guest atomic instructions
Date: Sat, 24 Apr 2010 03:49:02 +0100 [thread overview]
Message-ID: <20100424024902.GI15349@shareable.org> (raw)
In-Reply-To: <F5B96E9B-5179-4042-8917-CD10E26F4029@suse.de>
Alexander Graf wrote:
> They should be atomic. TCG SMP swaps between different vCPUs only
> after translation blocks are done. In fact, the only way I'm aware
> of to stop the execution of a TB mid-way is a page fault.
A page fault would interrupt it if the atomic is implemented as
a read followed by a write, and the write faults.
> You can as always check things with the -d parameter.
-- Jamie
next prev parent reply other threads:[~2010-04-24 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 17:27 [Qemu-devel] Atomicity of i386 guest atomic instructions Jakub Jermar
2010-04-23 20:57 ` Alexander Graf
2010-04-24 2:49 ` Jamie Lokier [this message]
2010-04-28 22:27 ` Paul Brook
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=20100424024902.GI15349@shareable.org \
--to=jamie@shareable.org \
--cc=agraf@suse.de \
--cc=jakub@jermar.eu \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).