[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] VTD/Intremap: Disable Intremap on Chipset 5500/5520/X58 due to errata

On Thu, 2013-01-17 at 09:09 +0000, Jan Beulich wrote:
> >>> On 17.01.13 at 10:01, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> > On Thu, 2013-01-17 at 08:49 +0000, Jan Beulich wrote:
> >> So the question really is whether, rather than disabling interrupt
> >> remapping, disabling the IOMMU as a whole wouldn't be the
> >> better (read: more secure) workaround. 
> > 
> > That, plus providing a command line "I accept the risks" option, is the
> > approach we've taken in the past I think.
> An option for this we already have - "iommu=force".

I thought that but isn't it sort of the other way found? iommu=force
will fail to boot if the iommu cannot be enabled, including intremap
support. But perhaps iommu=no-intremap does what we want already?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.