From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "R. Armiento" <reply-2006@armiento.net>
Subject: Re: [Qemu-devel] add 'monitor' and 'mwait' instruction (update)
Date: Sun, 9 Jul 2006 12:30:23 +0100 [thread overview]
Message-ID: <200607091230.24239.paul@codesourcery.com> (raw)
In-Reply-To: <44B10282.3060707@armiento.net>
> > Problem is, at the moment I've no idea, how we could achieve this memory
> > monitoring in a safe and simple way in user space.
>
> I'm trying to read up on monitor and mwait. Apparently mwait puts the
> processor in low-power wait mode, waiting for a memory write in some
> select area defined by monitor; and as I am new to this I'm not sure if
> I have understood all sources from where such a memory write can come
> from while the processor is asleep. One source, I suppose, is from other
> processors in an SMP setup? Another source may be DMA? Does this mean
> that it is safe to emulate wmait as hlt if neiter SMP or DMA is used?
> (Qemu hardware doesn't support DMA, right?)
qemu hardware does support DMA, but I don't think this matters.
By my reading DMA writes don't need to wake mwait.
The exact wording is "store operation", which I'd expect to mean execution of
a store instruction (by a different CPU). So for UP systems mwait can be
implemented the same as HLT, except that it raises an exception if state
hasn't been initialized by monitor.
Paul
next prev parent reply other threads:[~2006-07-09 11:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 15:13 [Qemu-devel] Pentium D with guest Ubuntu 6.06 server kernel panic with kqemu R. Armiento
2006-07-07 9:06 ` Joachim Henke
2006-07-07 9:39 ` Jens Axboe
2006-07-07 13:39 ` R. Armiento
2006-07-07 12:30 ` [Qemu-devel] [PATCH] add 'monitor' and 'mwait' instruction Joachim Henke
2006-07-07 12:57 ` maestro
2006-07-07 13:22 ` Joachim Henke
2006-07-07 15:21 ` Joachim Henke
2006-07-07 13:18 ` [Qemu-devel] [PATCH] add 'monitor' and 'mwait' instruction (update) Joachim Henke
2006-07-07 13:20 ` Joachim Henke
2006-07-08 13:16 ` R. Armiento
2006-07-08 15:01 ` [Qemu-devel] " Joachim Henke
2006-07-08 20:50 ` R. Armiento
2006-07-09 8:54 ` Joachim Henke
2006-07-09 13:20 ` R. Armiento
2006-07-09 11:30 ` Paul Brook [this message]
2006-07-09 15:25 ` Jamie Lokier
2006-07-09 13:03 ` [Qemu-devel] 'monitor' and 'mwait' instruction Joachim Henke
2006-07-09 15:21 ` [Qemu-devel] add 'monitor' and 'mwait' instruction (update) Jamie Lokier
2006-07-09 15:11 ` Jamie Lokier
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=200607091230.24239.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=reply-2006@armiento.net \
/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).