linux-kernel - [PATCH v2 08/12] drivers:pci:msi: Store PCI domain (segment) as part of IRQ domain

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 11 Sep 2015 00:01:07 +0000
From:	jakeo@...rosoft.com
To:	gregkh@...uxfoundation.org, kys@...rosoft.com,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	olaf@...fle.de, apw@...onical.com, vkuznets@...hat.com,
	linux-pci@...r.kernel.org, bhelgaas@...gle.com, tglx@...utronix.de
Cc:	Jake Oshins <jakeo@...rosoft.com>
Subject: [PATCH v2 08/12] drivers:pci:msi: Store PCI domain (segment) as part of IRQ domain

From: Jake Oshins <jakeo@...rosoft.com>

In order to allow an MSI IRQ domain to be specific to a PCI domain, add a field
to the struct that tracks the PCI domain.

Signed-off-by: Jake Oshins <jakeo@...rosoft.com>
---
 include/linux/msi.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/msi.h b/include/linux/msi.h
index ad939d0..7370225 100644
--- a/include/linux/msi.h
+++ b/include/linux/msi.h
@@ -227,6 +227,7 @@ struct msi_domain_ops {
  * @handler_data:	Optional: associated interrupt flow handler data
  * @handler_name:	Optional: associated interrupt flow handler name
  * @data:		Optional: domain specific data
+ * @pci_domain:		Associated PCI domain (segment)
  */
 struct msi_domain_info {
 	u32			flags;
@@ -237,6 +238,7 @@ struct msi_domain_info {
 	void			*handler_data;
 	const char		*handler_name;
 	void			*data;
+	int			pci_domain;
 };
 
 /* Flags for msi_domain_info */
-- 
1.9.1

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