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 for Android: free password hash cracker in your pocket

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

Message-ID: <jpgzj4fcywu.fsf@redhat.com>
Date:	Thu, 04 Jun 2015 10:48:33 -0400
From:	Bandan Das <bsd@...hat.com>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	alex.williamson@...hat.com
Subject: Re: [PATCH] kvm: x86: default legacy PCI device assignment support to "n"

Paolo Bonzini <pbonzini@...hat.com> 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 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?

Yeah, that is what I meant. The "Help" message does mention VFIO as the
newer option. Sometimes, seeing the word "DEPRECATED" makes one rethink if they
really need to enable it.

> Paolo
--
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/