From mboxrd@z Thu Jan  1 00:00:00 1970
From: ravi kerur <rkerur@gmail.com>
Subject: Re: Q on ioctl support in netfront/netback
Date: Wed, 17 Feb 2010 08:19:14 -0800
Message-ID: <dfc283f41002170819m7f150ba7s6729de4820fa238e@mail.gmail.com>
References: <dfc283f41002141823o7ca47994g7530e5cfc6ef7ad6@mail.gmail.com>
	<4B791671.4050902@citrix.com>
	<dfc283f41002150754w333813a4g15969fe418cba102@mail.gmail.com>
	<20100216181454.GD21067@phenom.dumpdata.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0423162425=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20100216181454.GD21067@phenom.dumpdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.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>
List-Id: xen-devel@lists.xenproject.org

--===============0423162425==
Content-Type: multipart/alternative; boundary=00235429d8fc1bc9b0047fce36a5

--00235429d8fc1bc9b0047fce36a5
Content-Type: text/plain; charset=ISO-8859-1

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.
>

--00235429d8fc1bc9b0047fce36a5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Konrad,<br><br>Using PCI passthrough(I believe it is via config file cha=
nges) prevents other domU&#39;s accessing the NIC correct? If I use it, wou=
ld the network transmit/receive still happen via netfront/netback drivers?<=
br>
<br>Thanks<br>-RK<br><br><div class=3D"gmail_quote">On Tue, Feb 16, 2010 at=
 10:14 AM, Konrad Rzeszutek Wilk <span dir=3D"ltr">&lt;<a href=3D"mailto:ko=
nrad.wilk@oracle.com">konrad.wilk@oracle.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, =
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class=3D"im">On Mon, Feb 15, 2010 at 07:54:02AM -0800, ravi kerur wrot=
e:<br>
&gt; Paul,<br>
&gt;<br>
&gt; Registers are not in netback, they are h/w registers on NIC and the dr=
iver<br>
&gt; supports reads/writes via ioctl calls. Driver is in dom0 and applicati=
on<br>
&gt; which reads/writes registers is run in domU.<br>
<br>
</div>You could use PCI passthrough. This way the NIC would be visible in y=
our<br>
DomU and you could fiddle with the registers.<br>
</blockquote></div><br>

--00235429d8fc1bc9b0047fce36a5--


--===============0423162425==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

--===============0423162425==--