linux-kernel - Re: [PATCH] kvm: Allow build-time configuration of KVM device assignment

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]

Message-Id: <59C4E05D-C3B5-4BDB-9285-D0CE8C30AFB7@suse.de>
Date:	Tue, 16 Apr 2013 23:17:30 +0200
From:	Alexander Graf <agraf@...e.de>
To:	Alex Williamson <alex.williamson@...hat.com>
Cc:	mtosatti@...hat.com, gleb@...hat.com, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kvm: Allow build-time configuration of KVM device assignment


On 16.04.2013, at 21:49, Alex Williamson wrote:

> We hope to at some point deprecate KVM legacy device assignment in
> favor of VFIO-based assignment.  Towards that end, allow legacy
> device assignment to be deconfigured.
> 
> Signed-off-by: Alex Williamson <alex.williamson@...hat.com>

Definitely a step into the right direction. And it should also fix a build error that I experienced with CONFIG_IOMMU and CONFIG_KVM on ppc and arm.


Reviewed-by: Alexander Graf <agraf@...e.de>

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