From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Host API escape
Date: Tue, 14 Sep 2004 06:07:26 +0100 [thread overview]
Message-ID: <20040914060726.A19722@edinburgh.cisco.com> (raw)
In-Reply-To: <E1C73HY-0002wj-9V@cell03.cell03.com>; from digitale@digitaleric.net on Mon, Sep 13, 2004 at 10:43:00PM -0400
On Mon, Sep 13, 2004 at 10:43:00PM -0400, EricNorthup wrote:
> Ok, I think the things you can achieve with this mechanism are very
> exciting. But please, *please* do not make another fork in x86!
Huh? What do you mean by "another fork in x86"? Or are you simply
referring to the fact that I've (re)defined a special instruction?
> What if you use the WRMSR instructions instead? Then you can define
> MSRs which have certain behavior when written to / read from. The whole
> point of MSRs is that they are model-specific, and that is the way to do
> this compatibly.
Hmm - a possibility.
I can look at changing to that once I've got the redir stuff working.
My initial concern was actually not to use / change any target visible
register, so that I can inject this anywhere as a debug hook - where
it's currently quite useful.
DF
next prev parent reply other threads:[~2004-09-14 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 2:43 [Qemu-devel] Host API escape EricNorthup
2004-09-14 5:07 ` Derek Fawcus [this message]
2004-09-14 5:23 ` [Qemu-devel] " Ben Pfaff
-- strict thread matches above, loose matches on Subject: below --
2004-09-12 21:17 [Qemu-devel] Patch: Bugfix in monitor, tidy in translate Derek Fawcus
2004-09-13 21:16 ` Fabrice Bellard
2004-09-13 22:45 ` [Qemu-devel] Host API escape Derek Fawcus
2004-09-14 7:54 ` Gwenole Beauchesne
2004-09-14 9:49 ` Derek Fawcus
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=20040914060726.A19722@edinburgh.cisco.com \
--to=dfawcus@cisco.com \
--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).