From: Rui Wang <rui.y.wang@intel.com>
To: helgaas@kernel.org, tglx@linutronix.de, rjw@rjwysocki.net
Cc: tony.luck@intel.com, bhelgaas@google.com,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, rui.y.wang@intel.com,
x86@kernel.org, fengguang.wu@intel.com, kbuild-all@01.org
Subject: [PATCH v2 0/2] Improvement on ioapic hotplug
Date: Tue, 28 Feb 2017 21:34:27 +0800 [thread overview]
Message-ID: <1488288869-31290-1-git-send-email-rui.y.wang@intel.com> (raw)
In-Reply-To: <201702280904.A2EXAFMQ%fengguang.wu@intel.com>
The revert of 991de2e59090 ("PCI, x86: Implement pcibios_alloc_irq()
and pcibios_free_irq()") causes a problem for IOAPIC hotplug. If
a device under the IOAPIC doesn't call pci_disable_device(), then
the hot-removal of the IOAPIC causes kernel stack dump.
This patchset can fix the problem. IOAPIC hot-removal works correctly
after applying this patchset.
v2: 0001 Fixed a missing stub function causing compiling error on i386
0002 Fixed a typo on the subject line.
Rui Wang (2):
x86/PCI: Implement pcibios_release_device to release IRQ from IOAPIC
x86/ioapic: Split IOAPIC hot-removal into two steps
arch/x86/pci/common.c | 9 +++++++++
drivers/acpi/internal.h | 2 ++
drivers/acpi/ioapic.c | 22 ++++++++++++++++------
drivers/acpi/pci_root.c | 4 ++--
4 files changed, 29 insertions(+), 8 deletions(-)
--
1.8.3.1
next parent reply other threads:[~2017-02-28 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201702280904.A2EXAFMQ%fengguang.wu@intel.com>
2017-02-28 13:34 ` Rui Wang [this message]
2017-02-28 13:34 ` [PATCH v2 1/2] x86/PCI: Implement pcibios_release_device to release IRQ from IOAPIC Rui Wang
2017-03-16 17:24 ` Bjorn Helgaas
2017-02-28 13:34 ` [PATCH v2 2/2] x86/ioapic: Split IOAPIC hot-removal into two steps Rui Wang
2017-03-16 17:48 ` Bjorn Helgaas
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=1488288869-31290-1-git-send-email-rui.y.wang@intel.com \
--to=rui.y.wang@intel.com \
--cc=bhelgaas@google.com \
--cc=fengguang.wu@intel.com \
--cc=helgaas@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).