Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-14 Thread Shashidhar Patil
Hi Alex,Jan, I put the hack of calling asssign_dev_msix_update() in mmio_msix_writel() when the last verctor of msix is updated. Now msix interrupt allocation happens as expected in the Host (Linux). But this is a ugly hack of hardcoding an address since we don't know how many msix vectors are

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-14 Thread Shashidhar Patil
Hi Alex,Jan, I forgot mention that in case of MSI-X failure I do not see any interrupts being allocated by the Host (kvm module). grep kvm /proc/interrupts is empty. -Shashidhar On Sat, Jan 14, 2012 at 12:16 PM, Shashidhar Patil wrote: > Hi Alex,Jan, >       I collected logs of pci updates p

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Shashidhar Patil
Hi Alex,Jan, I collected logs of pci updates processing of kvm(attached to this mail). (I will try your suggestion soon) The below source of Linux kernel shows the msix allocation done with MSIX_ENABLE_FLAG masked which works fine with kvm. static int msix_capability_init(struct pci_dev *d

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Jan Kiszka
On 2012-01-13 22:56, Alex Williamson wrote: > On Fri, 2012-01-13 at 22:33 +0100, Jan Kiszka wrote: >> On 2012-01-13 22:05, Alex Williamson wrote: >>> On Fri, 2012-01-13 at 22:00 +0100, Jan Kiszka wrote: On 2012-01-04 04:21, Alex Williamson wrote: > On Mon, 2011-12-19 at 19:49 +0530, Shashi

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Alex Williamson
On Fri, 2012-01-13 at 22:33 +0100, Jan Kiszka wrote: > On 2012-01-13 22:05, Alex Williamson wrote: > > On Fri, 2012-01-13 at 22:00 +0100, Jan Kiszka wrote: > >> On 2012-01-04 04:21, Alex Williamson wrote: > >>> On Mon, 2011-12-19 at 19:49 +0530, Shashidhar Patil wrote: > Hi, > I am

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Jan Kiszka
On 2012-01-13 22:05, Alex Williamson wrote: > On Fri, 2012-01-13 at 22:00 +0100, Jan Kiszka wrote: >> On 2012-01-04 04:21, Alex Williamson wrote: >>> On Mon, 2011-12-19 at 19:49 +0530, Shashidhar Patil wrote: Hi, I am running Ubuntu 10.10 (amd64) on a 2 socket nehalem based s

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Alex Williamson
On Fri, 2012-01-13 at 22:00 +0100, Jan Kiszka wrote: > On 2012-01-04 04:21, Alex Williamson wrote: > > On Mon, 2011-12-19 at 19:49 +0530, Shashidhar Patil wrote: > >> Hi, > >>I am running Ubuntu 10.10 (amd64) on a 2 socket nehalem based > >> server with IOH 5520. 5520 supports VTD. > >> I

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Jan Kiszka
On 2012-01-04 04:21, Alex Williamson wrote: > On Mon, 2011-12-19 at 19:49 +0530, Shashidhar Patil wrote: >> Hi, >>I am running Ubuntu 10.10 (amd64) on a 2 socket nehalem based >> server with IOH 5520. 5520 supports VTD. >> I enabled DMAR with intel_iommu=on. The box has intel 82599 adapter

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-13 Thread Alex Williamson
On Fri, 2012-01-13 at 12:25 +0530, Shashidhar Patil wrote: > Hi Alex, >Thanks for your help. Some answers and further investigation details > inline. > > On Wed, Jan 4, 2012 at 8:51 AM, Alex Williamson > wrote: > > > On Mon, 2011-12-19 at 19:49 +0530, Shashidhar Patil wrote: > > > Hi, > > >

Re: FreeBSD guest with VTD NIC not passing traffic

2012-01-03 Thread Alex Williamson
On Mon, 2011-12-19 at 19:49 +0530, Shashidhar Patil wrote: > Hi, >I am running Ubuntu 10.10 (amd64) on a 2 socket nehalem based > server with IOH 5520. 5520 supports VTD. > I enabled DMAR with intel_iommu=on. The box has intel 82599 adapter > which I assigned through VT-D to FreeBSD 8.2 ru

FreeBSD guest with VTD NIC not passing traffic

2011-12-19 Thread Shashidhar Patil
Hi, I am running Ubuntu 10.10 (amd64) on a 2 socket nehalem based server with IOH 5520. 5520 supports VTD. I enabled DMAR with intel_iommu=on. The box has intel 82599 adapter which I assigned through VT-D to FreeBSD 8.2 running as guest os. The ixgbe driver detects the device and the driver