From: ravi kerur <rkerur@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Paul Durrant <paul.durrant@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Q on ioctl support in netfront/netback
Date: Wed, 17 Feb 2010 08:19:14 -0800 [thread overview]
Message-ID: <dfc283f41002170819m7f150ba7s6729de4820fa238e@mail.gmail.com> (raw)
In-Reply-To: <20100216181454.GD21067@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]
Hi Konrad,
Using PCI passthrough(I believe it is via config file changes) prevents
other domU's accessing the NIC correct? If I use it, would the network
transmit/receive still happen via netfront/netback drivers?
Thanks
-RK
On Tue, Feb 16, 2010 at 10:14 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:
> On Mon, Feb 15, 2010 at 07:54:02AM -0800, ravi kerur wrote:
> > Paul,
> >
> > Registers are not in netback, they are h/w registers on NIC and the
> driver
> > supports reads/writes via ioctl calls. Driver is in dom0 and application
> > which reads/writes registers is run in domU.
>
> You could use PCI passthrough. This way the NIC would be visible in your
> DomU and you could fiddle with the registers.
>
[-- Attachment #1.2: Type: text/html, Size: 1071 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-02-17 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 2:23 Q on ioctl support in netfront/netback ravi kerur
2010-02-15 9:40 ` Paul Durrant
2010-02-15 15:54 ` ravi kerur
2010-02-16 18:14 ` Konrad Rzeszutek Wilk
2010-02-17 16:19 ` ravi kerur [this message]
2010-02-17 16:27 ` Pasi Kärkkäinen
2010-02-17 16:40 ` Konrad Rzeszutek Wilk
2010-02-17 20:00 ` ravi kerur
2010-02-17 3:26 ` Daniel Stodden
2010-02-17 15:44 ` ravi kerur
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=dfc283f41002170819m7f150ba7s6729de4820fa238e@mail.gmail.com \
--to=rkerur@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=paul.durrant@citrix.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 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).