From: Simon Martin <furryfuttock@gmail.com>
To: xen-devel@lists.xen.org
Subject: Realtime access to PCI NIC
Date: Mon, 7 Jul 2014 13:21:06 +0100 [thread overview]
Message-ID: <724187406.20140707132106@gmail.com> (raw)
In-Reply-To: <1083121389.20140707122233@gmail.com>
Hi all,
I am reading through the mini-os pcifront.c as an example of how to
implement direct access to a PCI device. However looking at the code
all access seems to go via the PCI Backend driver, which means that I
am subject to the latencies and jitter of the Xen scheduling.
Reading the documentation about PCI Passthrough I imagined that I
would have direct access to the PCI hardware once the handover from
dom0 as performed. Is that correct? If so, how do I implement that?
I am using an Intel processor that has VT-d so that should be
possible.
Any suggestions?
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next prev parent reply other threads:[~2014-07-07 12:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 11:13 Consuming PCI device in PV kernel Simon Martin
2014-07-03 18:09 ` Konrad Rzeszutek Wilk
2014-07-07 8:21 ` Simon Martin
2014-07-07 11:22 ` Simon Martin
2014-07-07 12:21 ` Simon Martin [this message]
2014-07-08 14:46 ` Realtime access to PCI NIC Ian Campbell
2014-07-10 7:47 ` Simon Martin
2014-07-08 15:01 ` Consuming PCI device in PV kernel Konrad Rzeszutek Wilk
2014-07-10 7:54 ` Simon Martin
2014-07-11 16:47 ` Dario Faggioli
2014-07-15 8:37 ` Simon Martin
2014-07-15 14:56 ` Konrad Rzeszutek Wilk
2014-07-18 14:37 ` Simon Martin
2014-07-18 19:09 ` Konrad Rzeszutek Wilk
2014-07-21 10:13 ` Simon Martin
2014-07-21 10:53 ` Ian Campbell
2014-07-25 12:56 ` Simon Martin
2014-07-25 13:10 ` Ian Campbell
2014-07-25 13:21 ` Simon Martin
2014-07-25 13:37 ` Ian Campbell
2014-07-25 13:50 ` Andrew Cooper
2014-07-25 14:20 ` Simon Martin
2014-07-25 14:25 ` Andrew Cooper
2014-07-25 14:30 ` Simon Martin
2014-07-25 14:33 ` Ian Campbell
2014-07-25 14:36 ` Simon Martin
2014-07-25 14:28 ` Simon Martin
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=724187406.20140707132106@gmail.com \
--to=furryfuttock@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).