linux-kernel - Re: [PATCH] kvm: Disable device assignment without interrupt remapping

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] [day] [month] [year] [list]

Message-ID: <20110719144304.GA31520@amt.cnet>
Date:	Tue, 19 Jul 2011 11:43:04 -0300
From:	Marcelo Tosatti <mtosatti@...hat.com>
To:	Alex Williamson <alex.williamson@...hat.com>
Cc:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	chrisw@...hat.com, ddutile@...hat.com,
	iommu@...ts.linux-foundation.org
Subject: Re: [PATCH] kvm: Disable device assignment without interrupt
 remapping

On Thu, Jul 14, 2011 at 01:27:03PM -0600, Alex Williamson wrote:
> IOMMU interrupt remapping support provides a further layer of
> isolation for device assignment by preventing arbitrary interrupt
> block DMA writes by a malicious guest from reaching the host.  By
> default, we should require that the platform provides interrupt
> remapping support, with an opt-in mechanism for existing behavior.
> 
> Both AMD IOMMU and Intel VT-d2 hardware support interrupt
> remapping, however we currently only have software support on
> the Intel side.  Users wishing to re-enable device assignment
> when interrupt remapping is not supported on the platform can
> use the "allow_unsafe_assigned_interrupts=1" module option.
> 
> Signed-off-by: Alex Williamson <alex.williamson@...hat.com>

Applied, thanks.

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