From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: Xin Tong <xerox.time.tech@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] memory ordering emulation in qemu
Date: Fri, 30 Mar 2012 09:40:43 +0800 [thread overview]
Message-ID: <20120330014043.GA28185@cs.nctu.edu.tw> (raw)
In-Reply-To: <CALKntY2AgLK1bzM+-_rdwRYJrbWxY1dP0PGY3OXds-JOCSYEyQ@mail.gmail.com>
On Thu, Mar 29, 2012 at 04:49:02PM -0400, Xin Tong wrote:
> I am wondering what the solution in qemu is if the guest architecture
> has a stronger memory ordering requirement than the host archiecture ?
> memory fences ?
There was a thread has a similar discussion. See
http://lists.gnu.org/archive/html/qemu-devel/2012-01/msg01897.html
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj
prev parent reply other threads:[~2012-03-30 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:49 [Qemu-devel] memory ordering emulation in qemu Xin Tong
2012-03-29 20:54 ` Peter Maydell
2012-03-30 1:40 ` 陳韋任 [this message]
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=20120330014043.GA28185@cs.nctu.edu.tw \
--to=chenwj@iis.sinica.edu.tw \
--cc=qemu-devel@nongnu.org \
--cc=xerox.time.tech@gmail.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;
as well as URLs for NNTP newsgroup(s).