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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 04 Jun 2015 08:47:17 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	Bandan Das <bsd@...hat.com>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Subject: Re: [PATCH] kvm: x86: default legacy PCI device assignment support
 to "n"

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 being tested on
> > > a wider variety of hardware these days than the legacy support.
> > >
> > > Disable legacy device assignment by default.
> >
> > Shouldn't we mark it as Deprecated then ?
> 
> Yes, good idea!  You mean just " (DEPRECATED)" after the string, right?

The ioctls should probably also be listed as deprecated in
Documentation/virtual/kvm/api.txt.  There's also
Documentation/ABI/obsolete if we intend to remove the code eventually.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/