From: Jiang Liu <liuj97@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
Yinghai Lu <yinghai@kernel.org>
Cc: Jiang Liu <liuj97@gmail.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Don Dutile <ddutile@redhat.com>,
Keping Chen <chenkeping@huawei.com>,
linux-pci@vger.kernel.org
Subject: [PATCH v5 0/6] PCI, x86: update MMCFG information when hot-plugging PCI host bridges
Date: Sat, 5 May 2012 11:00:24 +0800 [thread overview]
Message-ID: <1336186830-10765-1-git-send-email-jiang.liu@huawei.com> (raw)
From: Jiang Liu <liuj97@gmail.com>
This patchset enhance pci_root driver to update MMCFG information when
hot-plugging PCI root bridges. It applies to Yinghai's tree at
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-root-bus-hotplug
-v2: split into smaller patches and skip updating MMCFG information when
MMCFG is disabled
-v3: add mmconf_added to simply free path, also make pci_mmconfig_insert()
to process extra exist case --- By Yinghai
-v4: tune arch_acpi_pci_root_add() to handle a corner case raised by Kenji
-v5: address review comments from Bjorn and Taku, also better handle corner
cases in arch_acpi_pci_root_add()
Jiang Liu (6):
PCI, x86: split out pci_mmcfg_check_reserved() for code reuse
PCI, x86: split out pci_mmconfig_alloc() for code reuse
PCI, x86: use RCU list to protect mmconfig list
PCI, x86: introduce pci_mmcfg_arch_map()/pci_mmcfg_arch_unmap()
PCI, x86: introduce pci_mmconfig_insert()/delete() for PCI root
bridge hotplug
PCI, ACPI, x86: update MMCFG information when hot-plugging PCI host
bridges
arch/x86/include/asm/pci_x86.h | 5 +
arch/x86/pci/acpi.c | 57 +++++++++++
arch/x86/pci/mmconfig-shared.c | 203 +++++++++++++++++++++++++++++++---------
arch/x86/pci/mmconfig_32.c | 30 +++++-
arch/x86/pci/mmconfig_64.c | 37 +++++++-
drivers/acpi/pci_root.c | 22 +++++
include/acpi/acnames.h | 1 +
include/acpi/acpi_bus.h | 1 +
include/linux/pci-acpi.h | 4 +
9 files changed, 308 insertions(+), 52 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-05-05 3:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 3:00 Jiang Liu [this message]
2012-05-05 3:00 ` [PATCH v5 1/6] PCI, x86: split out pci_mmcfg_check_reserved() for code reuse Jiang Liu
2012-05-05 3:00 ` [PATCH v5 2/6] PCI, x86: split out pci_mmconfig_alloc() " Jiang Liu
2012-05-05 3:00 ` [PATCH v5 3/6] PCI, x86: use RCU list to protect mmconfig list Jiang Liu
2012-05-05 3:00 ` [PATCH v5 4/6] PCI, x86: introduce pci_mmcfg_arch_map()/pci_mmcfg_arch_unmap() Jiang Liu
2012-05-05 3:00 ` [PATCH v5 5/6] PCI, x86: introduce pci_mmconfig_insert()/delete() for PCI root bridge hotplug Jiang Liu
2012-05-18 16:30 ` Bjorn Helgaas
2012-05-05 3:00 ` [PATCH v5 6/6] PCI, ACPI, x86: update MMCFG information when hot-plugging PCI host bridges Jiang Liu
2012-05-18 16:03 ` Bjorn Helgaas
2012-05-18 16:56 ` Jiang Liu
2012-05-08 8:21 ` [PATCH v5 0/6] PCI, " Taku Izumi
2012-05-08 16:28 ` Bjorn Helgaas
2012-05-08 16:58 ` Jiang Liu
2012-05-09 7:21 ` Taku Izumi
2012-05-09 10:30 ` Jiang Liu
2012-05-18 16:36 ` Bjorn Helgaas
2012-05-18 16:59 ` Jiang Liu
2012-05-21 1:45 ` Taku Izumi
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=1336186830-10765-1-git-send-email-jiang.liu@huawei.com \
--to=liuj97@gmail.com \
--cc=bhelgaas@google.com \
--cc=chenkeping@huawei.com \
--cc=ddutile@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@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).