Re: [PATCH] kvm: x86: default legacy PCI device assignment support to "n"

2015-06-04 Thread Bandan Das
Paolo Bonzini writes: > On 04/06/2015 16:31, Bandan Das wrote: >> > VFIO has proved itself a much better option than KVM's built-in >> > device assignment. It is mature, provides better isolation because >> > it enforces ACS, and even the userspace code is being tested on >> > a wider variety of

Re: [PATCH] kvm: x86: default legacy PCI device assignment support to "n"

2015-06-04 Thread Alex Williamson
On Thu, 2015-06-04 at 16:33 +0200, Paolo Bonzini wrote: > > On 04/06/2015 16:31, Bandan Das wrote: > > > VFIO has proved itself a much better option than KVM's built-in > > > device assignment. It is mature, provides better isolation because > > > it enforces ACS, and even the userspace code is b

Re: [PATCH] kvm: x86: default legacy PCI device assignment support to "n"

2015-06-04 Thread Bandan Das
Paolo Bonzini writes: > VFIO has proved itself a much better option than KVM's built-in > device assignment. It is mature, provides better isolation because > it enforces ACS, and even the userspace code is being tested on > a wider variety of hardware these days than the legacy support. > > Dis

Re: [PATCH] kvm: x86: default legacy PCI device assignment support to "n"

2015-06-04 Thread Paolo Bonzini
On 04/06/2015 16:31, Bandan Das wrote: > > VFIO has proved itself a much better option than KVM's built-in > > device assignment. It is mature, provides better isolation because > > it enforces ACS, and even the userspace code is being tested on > > a wider variety of hardware these days than th

[PATCH] kvm: x86: default legacy PCI device assignment support to "n"

2015-06-04 Thread Paolo Bonzini
VFIO has proved itself a much better option than KVM's built-in device assignment. It is mature, provides better isolation because it enforces ACS, and even the userspace code is being tested on a wider variety of hardware these days than the legacy support. Disable legacy device assignment by de