On Thu, 2014-06-12 at 10:35 -0600, Alex Williamson wrote: > The user of the IOMMU API domain expects to have full control of > the IOVA space for the domain. RMRRs are fundamentally incompatible > with that idea. We can neither map the RMRR into the IOMMU API > domain, nor can we guarantee that the device won't continue DMA with > the area described by the RMRR as part of the new domain. Therefore > we must prevent such devices from being used by the IOMMU API. > > Signed-off-by: Alex Williamson <[email protected]> > --- > > I didn't see any actionable items from the last posting of this, so > re-posting unchanged.
That also wants a Cc:stable, I suppose. I note we now have two copies of the 'device has RMRR and we actually care' logic, where the latter clause is really just "is it USB". Is it worth consolidating that into a macro that's used in both places, in case the check does get more complicated? Are other devices going to start getting added to the class of "we don't need the RMRRs to persist and we *do* want to be able to assign them"... or is that just needlessly overcomplicating it at this stage? -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
