On Tue, Sep 23, 2014 at 04:46:01PM +0200, Antonios Motakis wrote: > Some IOMMUs accept an IOMMU_NOEXEC protection flag in addition to > IOMMU_READ and IOMMU_WRITE. Expose this as an IOMMU capability. > > Signed-off-by: Antonios Motakis <a.motakis@xxxxxxxxxxxxxxxxxxxxxx> > --- > include/linux/iommu.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/include/linux/iommu.h b/include/linux/iommu.h > index e1a644c..0433553 100644 > --- a/include/linux/iommu.h > +++ b/include/linux/iommu.h > @@ -59,6 +59,7 @@ struct iommu_domain { > > #define IOMMU_CAP_CACHE_COHERENCY 0x1 > #define IOMMU_CAP_INTR_REMAP 0x2 /* isolates device intrs */ > +#define IOMMU_CAP_NOEXEC 0x3 /* IOMMU_NOEXEC flag */ This changed recently to an enum, please rebase to latest iommu/next branch. With that change: Acked-by: Joerg Roedel <jroedel@xxxxxxx> for patches 1 and 2. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html