linux-kernel - [v5 3/9] iommu, x86: Abstract modify_irte() to accept two format of irte

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1432098937-19527-4-git-send-email-feng.wu@intel.com>
Date:	Wed, 20 May 2015 13:15:31 +0800
From:	Feng Wu <feng.wu@...el.com>
To:	joro@...tes.org, dwmw2@...radead.org
Cc:	tglx@...utronix.de, jiang.liu@...ux.intel.com,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Feng Wu <feng.wu@...el.com>
Subject: [v5 3/9] iommu, x86: Abstract modify_irte() to accept two format of irte

After introducing VT-d posted-interrupts, we have two format
of IRTE: remapped and posted. This patch make modify_irte()
suitable for both of them.

Signed-off-by: Feng Wu <feng.wu@...el.com>
---
 drivers/iommu/intel_irq_remapping.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/iommu/intel_irq_remapping.c b/drivers/iommu/intel_irq_remapping.c
index 8fad71c..1575b9e 100644
--- a/drivers/iommu/intel_irq_remapping.c
+++ b/drivers/iommu/intel_irq_remapping.c
@@ -122,11 +122,11 @@ static int qi_flush_iec(struct intel_iommu *iommu, int index, int mask)
 }
 
 static int modify_irte(struct irq_2_iommu *irq_iommu,
-		       struct irte *irte_modified)
+		       void *data)
 {
 	struct intel_iommu *iommu;
 	unsigned long flags;
-	struct irte *irte;
+	struct irte *irte, *irte_modified = (struct irte *)data;
 	int rc, index;
 
 	if (!irq_iommu)
-- 
2.1.0

--
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/