On Mon, Jul 12, 2010 at 09:29:38AM +0300, Avi Kivity wrote:
> On 07/11/2010 11:24 PM, Alex Williamson wrote:
> >
> >One other thing to be aware of is that vfio requires devices to be
> >PCI-2.3 compliant in order to support DisINTx. This allows vfio to
> >support devices making use of shared INTx
On 07/11/2010 11:24 PM, Alex Williamson wrote:
One other thing to be aware of is that vfio requires devices to be
PCI-2.3 compliant in order to support DisINTx. This allows vfio to
support devices making use of shared INTx interrupts, but excludes older
devices that users maybe managed to get a
On Sun, 2010-07-11 at 21:43 +0300, Avi Kivity wrote:
> On 07/11/2010 09:37 PM, Alex Williamson wrote:
> > On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
> >
> >> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> >>
> >>> The following series implements QEMU device assignment using th
On 07/11/2010 09:37 PM, Alex Williamson wrote:
On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
On 07/11/2010 09:09 PM, Alex Williamson wrote:
The following series implements QEMU device assignment using the
proposed VFIO/UIOMMU kernel interfaces. See the last patch for
further v
On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > The following series implements QEMU device assignment using the
> > proposed VFIO/UIOMMU kernel interfaces. See the last patch for
> > further vfio description. I've tested this on the v2 VF
On 07/11/2010 09:09 PM, Alex Williamson wrote:
The following series implements QEMU device assignment using the
proposed VFIO/UIOMMU kernel interfaces. See the last patch for
further vfio description. I've tested this on the v2 VFIO patch,
with a number of fixes hacked in along the way. I'll u
