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:	Mon, 9 May 2016 13:49:27 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
Cc:	pbonzini@...hat.com, rkrcmar@...hat.com, bp@...en8.de,
	gleb@...nel.org, alex.williamson@...hat.com, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, wei@...hat.com,
	sherry.hurwitz@....com
Subject: Re: [PART2 RFC v1 1/9] iommu/amd: Detect and enable guest vAPIC
 support

On Fri, Apr 08, 2016 at 07:49:22AM -0500, Suthikulpanit, Suravee wrote:
> From: Suravee Suthikulpanit <suravee.suthikulpanit@....com>
> 
> This patch introduces a new IOMMU driver parameter, amd_iommu_guest_ir,
> which can be used to specify different interrupt remapping mode for
> passthrough devices to VM guest:
>     * legacy: Legacy interrupt remapping mode (w/ 32-bit IRTE)
>     * ga    : Guest vAPIC interrupt remapping mode (w/ 128-bit IRTE)
> 
> Note that the GA mode also supports legacy interrupt remapping
> for non-passthrough devices with the 128-bit IRTE.

Does this need to be under user control? The code can just check what
the hardware supports and use the 128bit IRTEs if supported, no?



	Joerg

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ