From: Jiang Liu <liuj97@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Ingo Molnar <mingo@elte.hu>
Cc: Jiang Liu <liuj97@gmail.com>, Keping Chen <chenkeping@huawei.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [PATCH v1 0/3] enhance DCA core to support DCA device hotplug
Date: Mon, 23 Apr 2012 22:33:59 +0800 [thread overview]
Message-ID: <1335191642-6869-1-git-send-email-jiang.liu@huawei.com> (raw)
From: Jiang Liu <liuj97@gmail.com>
When hot-removing PCI host bridges on Intel platforms, all endpoint devices
built in the PCI host bridge (IOH) should be removed too. This patchset
enhances the DCA core logic to support hotplug of Intel Crystall Beach PCI
devices built in the IOH. It also enhances the core to support multiple
PCI root complexes (domains).
The patchset applies to the mainline kernel at
cdd5983 Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost
and it has been tested on an IBM x3850 system.
Jiang Liu (3):
DCA, x86: fix invalid memory access in DCA core
DCA, x86: restart DCA operations in unregister_dca_provider()
DCA, x86: support mutitple PCI root complexes in DCA core logic
drivers/dca/dca-core.c | 152 ++++++++++++++++++++++++------------------------
1 files changed, 77 insertions(+), 75 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-04-23 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 14:33 Jiang Liu [this message]
2012-04-23 14:34 ` [PATCH v1 1/3] DCA, x86: fix invalid memory access in DCA core Jiang Liu
2012-04-23 14:34 ` [PATCH v1 2/3] DCA, x86: restart DCA operations in unregister_dca_provider() Jiang Liu
2012-04-23 14:34 ` [PATCH v1 3/3] DCA, x86: support mutitple PCI root complexes in DCA core logic Jiang Liu
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=1335191642-6869-1-git-send-email-jiang.liu@huawei.com \
--to=liuj97@gmail.com \
--cc=chenkeping@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).