From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Keir Fraser <keir.xen@gmail.com>
Subject: [help]: handling IO instructions for hybrid
Date: Mon, 6 Feb 2012 18:26:54 -0800 [thread overview]
Message-ID: <20120206182654.5b5d3f2d@mantra.us.oracle.com> (raw)
Hi all,
I am figuring io access for hybrid guests, dom0 and domU. I see that there
are two ways: PV -> emulate_privileged_op(), or hvm handles via
handle_mmio()/handle_pio(). I am not familiar with either one, and would
help me lot if anybody expert in that can suggest which way
hybrid should go, both dom0 and domU. Any suggestions would help. If
there are any docs on this, that would be great too.
thanks,
Mukesh
next reply other threads:[~2012-02-07 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 2:26 Mukesh Rathor [this message]
2012-02-06 19:41 ` [help]: handling IO instructions for hybrid Keir Fraser
2012-02-09 2:17 ` Mukesh Rathor
2012-02-09 3:18 ` Keir Fraser
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=20120206182654.5b5d3f2d@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.xen@gmail.com \
--cc=stefano.stabellini@eu.citrix.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).