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-next>] [day] [month] [year] [list]
Message-Id: <1416048553-29289-1-git-send-email-marc.zyngier@arm.com>
Date:	Sat, 15 Nov 2014 10:49:11 +0000
From:	Marc Zyngier <marc.zyngier@....com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Jiang Liu <jiang.liu@...ux.intel.com>
Cc:	Yingjoe Chen <yingjoe.chen@...iatek.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: [PATCH 0/2] Stacked domains and MSI improvements

This short series builds upon Jiang Liu's MSI stacked domain and tries
to clean up a couple of points:

- Patch 1 allows an msi_chip to carry a pointer to its irq domain.
  When populated by the MSI driver, this allow the PCI bus to be
  associated with an irq domain, removing most of the need for arch
  specific code in the case of multiple PCI busses.

- Patch 2 tries to work around a limitation of __irq_set_handler when
  called with an interrupt belongging to a stacked domain.

This has been tested on arm64, together with the GICv3 ITS.

Marc Zyngier (2):
  PCI/MSI: Allow an msi_chip to be associated to an irq domain
  genirq: Work around __irq_set_handler vs stacked domains ordering
    issues

 drivers/pci/msi.c   | 16 +++++++++++++++-
 include/linux/msi.h |  3 +++
 kernel/irq/chip.c   | 11 ++++++++++-
 3 files changed, 28 insertions(+), 2 deletions(-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ