From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ritu kaur <ritu.kaur.us@gmail.com>
Cc: Daniel,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"djmagee@mageenet.net" <djmagee@mageenet.net>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stodden <Daniel.Stodden@citrix.com>
Subject: Re: Shared memory and event channel
Date: Wed, 24 Feb 2010 09:38:33 +0000 [thread overview]
Message-ID: <1267004313.11737.7501.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <29b32d341002231126h703334b2u5af6ab9b2bbf00fc@mail.gmail.com>
On Tue, 2010-02-23 at 19:26 +0000, Ritu kaur wrote:
> Need a clarification, using pci passthrough I believe it remove access
> to device from dom0 and attaches the device to a domU and from then on
> can only be accessed via that domU or is it possible to have dom0 and
> a single domU gain access to device using pci passthrough? I guess
> not, thought of checking.
You are correct, a given hardware device is only directly accessible to
a single domain at a time, be that dom0 or a domU via PCI passthrough.
Ian.
next prev parent reply other threads:[~2010-02-24 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29b32d341002211058l7e283336pa4fdfd0dc0b7124b@mail.gmail.com>
[not found] ` <1266787199.24577.18.camel@agari.van.xensource.com>
2010-02-21 23:33 ` Shared memory and event channel Ritu kaur
2010-02-22 7:55 ` Daniel Stodden
2010-02-22 17:36 ` Ritu kaur
2010-02-22 21:34 ` Daniel Stodden
2010-02-22 22:16 ` Ritu kaur
2010-02-23 9:38 ` Ian Campbell
2010-02-23 14:47 ` Konrad Rzeszutek Wilk
2010-02-23 15:42 ` Ian Campbell
2010-02-23 15:53 ` Ritu kaur
2010-02-23 17:42 ` djmagee
2010-02-23 19:26 ` Ritu kaur
2010-02-24 9:38 ` Ian Campbell [this message]
2007-11-19 7:59 shared " Amit Singh
2007-11-28 1:45 ` Mark Williamson
2007-12-21 8:39 ` tgh
2007-12-21 12:54 ` 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=1267004313.11737.7501.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Daniel.Stodden@citrix.com \
--cc=djmagee@mageenet.net \
--cc=konrad.wilk@oracle.com \
--cc=ritu.kaur.us@gmail.com \
--cc=xen-devel@lists.xensource.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 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.