[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1433926501-22956-1-git-send-email-jiang.liu@linux.intel.com>
Date: Wed, 10 Jun 2015 16:54:57 +0800
From: Jiang Liu <jiang.liu@...ux.intel.com>
To: Thomas Gleixner <tglx@...utronix.de>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Jiang Liu <jiang.liu@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org,
linux-acpi@...r.kernel.org, "x86 @ kernel . org" <x86@...nel.org>
Subject: [Patch v3 0/4] Introduce a mechanism to allocate PCI IRQ on demand
Hi Bjorn,
I have verified that this patch set could be applied to the
mainstream kernel without dependency on other patches, so could you
please help to merge it?
This patch set introduces a mechanism to allocate PCI IRQ on demand and
free it when not used anymore by hooking pci_device_probe() and
pci_device_remove().
It will be used to track IOAPIC pin usage on x86 so we could support
IOAPIC hot-removal.
The patch set passes Fengguang's 0day test suite.
V2->V3:
1) Change the default pcibios_alloc_irq() to always return 0, as
suggested by Bjorn.
2) Refine comments.
V1->V2:
1) Refine pci_device_probe() to optimize for mainline code as suggested
by Bjorn
2) Reorder patch set to put optional patch as the last (Patch 4)
Jiang Liu (4):
PCI: Add hooks to allocate/free IRQ resources when binding/unbinding
driver
PCI, x86: Allocate PCI IRQ on demand and free it when not used
anymore
PCI: Add helpers to manage pci_dev->irq and pci_dev->irq_managed
PCI, MSI: Free legacy PCI IRQ when enabling MSI/MSI-X
arch/x86/include/asm/pci_x86.h | 2 --
arch/x86/pci/common.c | 20 +++++++++-----------
arch/x86/pci/intel_mid_pci.c | 9 ++++++---
arch/x86/pci/irq.c | 23 ++++-------------------
drivers/acpi/pci_irq.c | 17 ++++-------------
drivers/pci/msi.c | 6 +++++-
drivers/pci/pci-driver.c | 26 ++++++++++++++++++++------
include/linux/pci.h | 19 +++++++++++++++++++
8 files changed, 67 insertions(+), 55 deletions(-)
--
1.7.10.4
--
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