From: Nitin Gupta <nitin.kobain@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: DomU trying to write on an IO Port
Date: Mon, 18 Feb 2013 19:42:41 +0530 [thread overview]
Message-ID: <CAESzvYTNqPWctyw3i+7nWGSnNrerS7DrgLhWVUK3_6Prw=xUgw@mail.gmail.com> (raw)
In-Reply-To: <1361195180.31407.164.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]
I am running Xen in a virtual machine provided by qemu (qemu-system
emulation) without KVM.
On Mon, Feb 18, 2013 at 7:16 PM, Ian Campbell <Ian.Campbell@citrix.com>wrote:
> On Mon, 2013-02-18 at 12:31 +0000, Nitin Gupta wrote:
> > Hi,
> >
> >
> > I am running xen-hypervisor over qemu.
>
> You mean running Xen in a virtual machine provided by qemu? Or are you
> talking about the qemu which is associated with an HVM domain under Xen
> (i.e. the one running in dom0 or a stub domain).
>
> > Now while running domU I want to write on an IO port, which I'll be
> > handling inside Qemu. Basically, this is a communication mechanism for
> > me to communicate with qemu. I am writing on port number '0x378' as a
> > root user using "outl" function. But when I run this code in domU, it
> > does not reach qemu.
> >
> > So my question is: Is there some mechanism in xen which handles
> > writing on IO ports and in case its not a valid IO Port then just
> > discards the write.
> >
> > --
> > Regards,
> > Nitin Gupta
> >
> >
>
>
>
--
Regards,
Nitin Gupta
M.Tech. CSE, IIT Delhi
[-- Attachment #1.2: Type: text/html, Size: 1656 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-02-18 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 12:31 DomU trying to write on an IO Port Nitin Gupta
2013-02-18 13:46 ` Ian Campbell
2013-02-18 14:12 ` Nitin Gupta [this message]
2013-02-18 14:20 ` Ian Campbell
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='CAESzvYTNqPWctyw3i+7nWGSnNrerS7DrgLhWVUK3_6Prw=xUgw@mail.gmail.com' \
--to=nitin.kobain@gmail.com \
--cc=Ian.Campbell@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.