[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Q on ioctl support in netfront/netback


  • To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • From: ravi kerur <rkerur@xxxxxxxxx>
  • Date: Wed, 17 Feb 2010 08:19:14 -0800
  • Cc: Paul Durrant <paul.durrant@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 17 Feb 2010 08:20:05 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iS8kcjw8kJVdEwt5W9bo4VIRYw29kSubi1HgeoCOR1bywcZwuiJVNikHhJ2SmN6ho9 VXd27zsT6oU+Gw+E41zPc9waEYaKcf32HgoILFGDNtRnjVar7YBK7N18gSKO89RdGrgt //vRVZJFjFYnb2JgY01Pc0z6iCy4h2d0tXQxI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.