From: Keith Busch <keith.busch@intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-pci@vger.kernel.org
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dan Williams <dan.j.williams@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Bryan Veal <bryan.e.veal@intel.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Martin Mares <mj@ucw.cz>,
Jon Derrick <jonathan.derrick@intel.com>,
Keith Busch <keith.busch@intel.com>
Subject: [PATCHv4 0/6] Driver for new VMD device
Date: Fri, 6 Nov 2015 15:35:40 -0700 [thread overview]
Message-ID: <1446849346-8242-1-git-send-email-keith.busch@intel.com> (raw)
Version 4 after re-working the irq domain hierarchies.
v3 -> v4:
Patch from Jiang to allow parent-less msi irq domain.
Separated kernel API dependency exports into their own patch.
Removed the vmd irq domain hierarchy, and instead use a msi irq
domain. This pushed all the irq initialization and teardown handling
into the irq_chip implementation and reduced kernel dependencies.
Using devm_request_irq instead of an irq flow handler. This moves the
irq life management to the devres API which simplifies teardown.
Implemented a smarter method of selecting the VMD vector to share.
Lots style fixes/updates and additional code comments.
The one review comment I have not fixed is the affinity hint. We are
still developing a way to better handle this, so have left it as a error
returning stub. It's less than optimal, but isn't more harmful than that.
Keith Busch (5):
pci: skip child bus with conflicting resources
Export msi and irq functions for module use
x86-pci: allow pci domain specific dma ops
x86/pci: Initial commit for new VMD device driver
pciutils: Allow 32-bit domains
Liu Jiang (1):
msi: Relax msi_domain_alloc() to support parentless MSI irqdomains
arch/x86/Kconfig | 13 +
arch/x86/include/asm/device.h | 10 +
arch/x86/include/asm/hw_irq.h | 5 +
arch/x86/pci/Makefile | 2 +
arch/x86/pci/common.c | 38 +++
arch/x86/pci/vmd.c | 646 ++++++++++++++++++++++++++++++++++++++++++
drivers/pci/msi.c | 2 +
drivers/pci/probe.c | 10 +-
kernel/irq/irqdomain.c | 1 +
kernel/irq/msi.c | 8 +-
10 files changed, 730 insertions(+), 5 deletions(-)
create mode 100644 arch/x86/pci/vmd.c
--
2.6.2.307.g37023ba
next reply other threads:[~2015-11-06 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 22:35 Keith Busch [this message]
2015-11-06 22:35 ` [PATCHv4 1/6] msi: Relax msi_domain_alloc() to support parentless MSI irqdomains Keith Busch
2015-11-07 11:43 ` Thomas Gleixner
2015-11-06 22:35 ` [PATCHv4 2/6] pci: skip child bus with conflicting resources Keith Busch
2015-11-06 22:35 ` [PATCHv4 3/6] Export msi and irq functions for module use Keith Busch
2015-11-06 22:35 ` [PATCHv4 4/6] x86-pci: allow pci domain specific dma ops Keith Busch
2015-11-06 22:35 ` [PATCHv4 5/6] x86/pci: Initial commit for new VMD device driver Keith Busch
2015-11-07 11:55 ` Thomas Gleixner
2015-11-06 22:35 ` [PATCHv4 6/6] pciutils: Allow 32-bit domains Keith Busch
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=1446849346-8242-1-git-send-email-keith.busch@intel.com \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=bryan.e.veal@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mj@ucw.cz \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.