[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1401987808-23596-3-git-send-email-a.motakis@virtualopensystems.com>
Date: Thu, 5 Jun 2014 19:03:10 +0200
From: Antonios Motakis <a.motakis@...tualopensystems.com>
To: alex.williamson@...hat.com, kvmarm@...ts.cs.columbia.edu,
iommu@...ts.linux-foundation.org
Cc: tech@...tualopensystems.com, a.rigo@...tualopensystems.com,
kvm@...r.kernel.org, christoffer.dall@...aro.org,
will.deacon@....com, kim.phillips@...escale.com,
stuart.yoder@...escale.com, eric.auger@...aro.org,
Antonios Motakis <a.motakis@...tualopensystems.com>,
Joerg Roedel <joro@...tes.org>,
Varun Sethi <Varun.Sethi@...escale.com>,
Alexey Kardashevskiy <aik@...abs.ru>,
Shuah Khan <shuah.kh@...sung.com>,
"Upinder Malhi (umalhi)" <umalhi@...co.com>,
linux-kernel@...r.kernel.org (open list)
Subject: [RFC PATCH v6 02/20] iommu: add capability IOMMU_CAP_NOEXEC
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@...tualopensystems.com>
---
include/linux/iommu.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linux/iommu.h b/include/linux/iommu.h
index fc464d2..7e152fb 100644
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@ -57,8 +57,9 @@ struct iommu_domain {
struct iommu_domain_geometry geometry;
};
-#define IOMMU_CAP_CACHE_COHERENCY 0x1
-#define IOMMU_CAP_INTR_REMAP 0x2 /* isolates device intrs */
+#define IOMMU_CAP_CACHE_COHERENCY (1 << 0)
+#define IOMMU_CAP_INTR_REMAP (1 << 1) /* isolates device intrs */
+#define IOMMU_CAP_NOEXEC (1 << 2) /* IOMMU_NOEXEC flag */
/*
* Following constraints are specifc to FSL_PAMUV1:
--
1.8.3.2
--
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/
Powered by blists - more mailing lists