From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Nitin Gupta <nitin.kobain@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: domu to dom0's entry point
Date: Mon, 17 Sep 2012 10:27:36 -0400 [thread overview]
Message-ID: <20120917142734.GA14012@phenom.dumpdata.com> (raw)
In-Reply-To: <CAESzvYTsHm+QYiP6TCYXUC3AWfP-LuzvxOVYN7bnd6MF=a3v6Q@mail.gmail.com>
On Sat, Sep 15, 2012 at 07:00:56PM +0530, Nitin Gupta wrote:
> Hi,
>
> I have a query.
>
> Dom0 is the administrative kernel which can access I/O devices through
> hypervisor. So if an application wants to write to an I/O device then it
> should go through Dom0. Is it right? If its so then can anyone point to the
No. It will go to the hypervisor if the DomU has been granted access
to those I/O ports/MMIO bars..
> entry and exit points in Dom0.
>
> --
> Regards,
> Nitin Gupta
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-09-17 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 13:30 domu to dom0's entry point Nitin Gupta
2012-09-17 14:27 ` Konrad Rzeszutek Wilk [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=20120917142734.GA14012@phenom.dumpdata.com \
--to=konrad@kernel.org \
--cc=nitin.kobain@gmail.com \
--cc=xen-devel@lists.xen.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).