[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1411483586-29304-3-git-send-email-a.motakis@virtualopensystems.com>
Date: Tue, 23 Sep 2014 16:46:01 +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, kvm@...r.kernel.org,
christoffer.dall@...aro.org, will.deacon@....com,
kim.phillips@...escale.com, eric.auger@...aro.org,
marc.zyngier@....com,
Antonios Motakis <a.motakis@...tualopensystems.com>,
Joerg Roedel <jroedel@...e.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Shuah Khan <shuah.kh@...sung.com>,
Thierry Reding <treding@...dia.com>,
Alexey Kardashevskiy <aik@...abs.ru>,
"Upinder Malhi (umalhi)" <umalhi@...co.com>,
linux-kernel@...r.kernel.org (open list)
Subject: [PATCHv7 02/26] 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 | 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 */
/*
* 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