From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>
Cc: Yingjoe Chen <yingjoe.chen@mediatek.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Stacked domains and MSI improvements
Date: Sat, 15 Nov 2014 10:49:11 +0000 [thread overview]
Message-ID: <1416048553-29289-1-git-send-email-marc.zyngier@arm.com> (raw)
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
next reply other threads:[~2014-11-15 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 10:49 Marc Zyngier [this message]
2014-11-15 10:49 ` [PATCH 1/2] PCI/MSI: Allow an msi_chip to be associated to an irq domain Marc Zyngier
2014-11-23 18:14 ` [tip:irq/irqdomain] PCI/MSI: Allow an msi_controller " tip-bot for Marc Zyngier
2014-11-15 10:49 ` [PATCH 2/2] genirq: Work around __irq_set_handler vs stacked domains ordering issues Marc Zyngier
2014-11-23 18:11 ` [tip:irq/irqdomain] " tip-bot for Marc Zyngier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1416048553-29289-1-git-send-email-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=bhelgaas@google.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yingjoe.chen@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®