From: Jiang Liu <liuj97@gmail.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Jiang Liu <jiang.liu@huawei.com>
Subject: Re: [PATCH v1 0/8] enhance dmaengine core to support DMA device hotplug
Date: Thu, 17 May 2012 23:43:05 +0800 [thread overview]
Message-ID: <4FB51C89.5080905@gmail.com> (raw)
>On Mon, Apr 23, 2012 at 6:51 AM, Jiang Liu <liuj97@xxxxxxxxx> wrote:
>> From: Jiang Liu <liuj97@xxxxxxxxx>
>>
>> This patchset tries to enhance the dmaengine and its clients to support
>> hot-removal of DMA devices at runtime, especially for IOAT devices.
>>
>> When hot-removing IOH (PCI host bridge) on Intel Nehalem/Westmere platform,
>> we need to remove all IOAT devices embedded in the IOH. For future Intel
>> processor with IIO (Embedded IOH), we need to remove IOAT devices even
>> when hot-removing a physical processor. But current dmaengine implementation
>> doesn't support hot-removal of IOAT devices at runtime.
>
>Removal of the host bridge means several devices disappear at once.
>Is it safe to assume that this action is coordinated by userspace?
>I.e. is the kernel given a chance to shut everything down and remove
>drivers, or is this a "surprise" unplug?
Hi Dan,
Sorry for late reply! I just noticed this mail by browsing the linux-pci
mail list web archive just now.
Yes, it will be coordinated by user/kernel hotplug manager. We don't
plan to support surprisingly removal yet. It seems a little craze to support
that.
Thanks!
Gerry
next reply other threads:[~2012-05-17 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 15:43 Jiang Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-23 13:51 [PATCH v1 0/8] enhance dmaengine core to support DMA device hotplug Jiang Liu
2012-04-23 16:40 ` Dan Williams
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=4FB51C89.5080905@gmail.com \
--to=liuj97@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=jiang.liu@huawei.com \
--cc=linux-pci@vger.kernel.org \
--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 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.