From: Ben Pfaff <blp@cs.stanford.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Host API escape
Date: Mon, 13 Sep 2004 22:23:48 -0700 [thread overview]
Message-ID: <87acvt4e57.fsf@benpfaff.org> (raw)
In-Reply-To: 20040914060726.A19722@edinburgh.cisco.com
Derek Fawcus <dfawcus@cisco.com> writes:
> On Mon, Sep 13, 2004 at 10:43:00PM -0400, EricNorthup wrote:
>> 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.
For what it's worth, VMware products use a magic I/O port for
guest<->host communication according to
http://chitchat.at.infoseek.co.jp/vmware/backdoor.html
--
Ben Pfaff
email: blp@cs.stanford.edu
web: http://benpfaff.org
prev parent reply other threads:[~2004-09-14 5:29 UTC|newest]
Thread overview: 3+ 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
2004-09-14 5:23 ` Ben Pfaff [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=87acvt4e57.fsf@benpfaff.org \
--to=blp@cs.stanford.edu \
--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).