From: sanket hase <shase@andrew.cmu.edu>
To: xen-devel@lists.xensource.com
Cc: xen-users@lists.xensource.com
Subject: Passthrough support ?
Date: Mon, 26 Nov 2007 19:02:32 -0500 [thread overview]
Message-ID: <474B5E98.1060302@andrew.cmu.edu> (raw)
Hi ,
I have been trying to understand PCI -passthrough support. Please
correct me if I am wrong in my following inferences.
1. Device emulation and pass through are both implemented using split
drivers.
2. But, in case of emulation drivers of dom0 are used where as in case
of passthrough ( as the name suggests ) native drivers in domU are used .
3. dom0 provides a virtual PCI device { an interface for device-OPs and
status of this virtual device} to domU and through associated event
channel domU makes
"synchronous" use of this device.
===
Queries:
1. What i am really not so sure about is ... passthrough case
Will there be requirement to map the address space of this PCI
device in domU ? Will the page which was being shared so-far
{xen_pci_sharedinfo}
for emulation , be "flipped" ( transferred ) into domU ? 2. Well ,
Having read the code for linux (dom0,domU) I see that there are split
device drivers for PCI. (pci front and PCIback). Which are normally
communicating over xenbus. which looks almost like other split
drivers. How exactly then passthrough enables use of domU's drivers ?
3. And if passthrough support isnt provided how will communication
between pcifront-pciback be different ? ( I guess netbsd , freebsd do
not have passthrough support yet )
4. What restricts other domUs from accessing PCI device given to other
domU via passrthrough support.
Regards,
Sanket
next reply other threads:[~2007-11-27 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 0:02 sanket hase [this message]
2007-11-27 20:55 ` Passthrough support ? Mark Williamson
2007-11-28 1:27 ` [Xen-users] " sanket hase
2007-11-28 2:19 ` Mark Williamson
2007-11-28 3:02 ` [Xen-devel] " sanket hase
2007-11-28 3:14 ` Re: [Xen-users] " Mark Williamson
2007-11-28 1:30 ` sanket hase
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=474B5E98.1060302@andrew.cmu.edu \
--to=shase@andrew.cmu.edu \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.