From: Jiang Liu <liuj97@gmail.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org, bhelgaas@google.com,
shuahkhan@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/7] ACPI: Add CONFIG_HOTPLUG_OST option
Date: Fri, 11 May 2012 08:15:26 +0800 [thread overview]
Message-ID: <4FAC5A1E.3090602@gmail.com> (raw)
In-Reply-To: <1336674019.16730.239.camel@misato.fc.hp.com>
On 05/11/2012 02:20 AM, Toshi Kani wrote:
> On Fri, 2012-05-11 at 01:43 +0800, Jiang Liu wrote:
>> On 05/11/2012 01:26 AM, Toshi Kani wrote:
>>> On Fri, 2012-05-11 at 00:40 +0800, Jiang Liu wrote:
>>>> On 05/09/2012 04:12 AM, Toshi Kani wrote:
>>>>> Added CONFIG_ACPI_HOTPLUG_OPT option. When this config option is disabled,
>>>>> this patchset has no effect on the platform. This option is disabled by
>>>>> default. The dependency list assures consistent behavior among CPU, memory
>>>>> and container hotplug operations with regarding the _OST support.
>>>> Seems also need to enhance the acpiphp driver for PCI hotplug operations too.
>>>> acpiphp driver is also based on the ACPI device hotplug model.
>>>
>>> Good question. ACPI PCI hotplug is a legacy method, which is being
>>> replaced by PCI native hotplug. I expect PCI native hotplug will be
>>> used for any platforms supporting PCI-E. Since this _OST support is
>>> targeted for new platforms (as _OST is not supported on the current
>>> platforms), I thought that it would be prudent to avoid changing PCI
>>> hotplug code for this.
>> You are right, acpiphp is legacy method. But it may also be used to support
>> some cases which can't be supported by the pciehp driver.
>> For example, we have a PCIe system which needs to run acpiphp and pciehp
>> concurrently. The pciehp driver is used to manage hot-pluggable PCIe slot,
>> and the acpiphp driver is used to migrate downstream ports among virtual
>> PCIe switches of an MR-IOV switch. It would be great if we could enable
>> _OST for acpiphp too.
>>
>> To be honest, our BIOS doesn't provide _OST for acpiphp yet, so we could
>> enhance acpiphp driver in future when a system really needing that feature
>> appears.
>
> Interesting. In such case, I am willing to change acpiphp, but I am
> afraid that I do not have access to platforms with ACPI PCI hotplug
> support. My test systems are all PCI-E based. So, it would be great if
> you could enhance acpiphp when you need it.
Sure, I will enhance it based on your work when needed.
Thanks!
-Gerry
>
>
> Thanks!
> -Toshi
>
next prev parent reply other threads:[~2012-05-11 0:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 20:12 [PATCH v2 0/7] ACPI: Add _OST support for ACPI hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 1/7] ACPI: Add CONFIG_HOTPLUG_OST option Toshi Kani
2012-05-10 16:40 ` Jiang Liu
2012-05-10 17:26 ` Toshi Kani
2012-05-10 17:43 ` Jiang Liu
2012-05-10 18:20 ` Toshi Kani
2012-05-11 0:15 ` Jiang Liu [this message]
2012-05-08 20:12 ` [PATCH v2 2/7] ACPI: Add an interface to evaluate _OST Toshi Kani
2012-05-08 20:12 ` [PATCH v2 3/7] ACPI: Add _OST support for sysfs eject Toshi Kani
2012-05-09 16:46 ` Shuah Khan
2012-05-09 18:16 ` Toshi Kani
2012-05-10 15:40 ` Shuah Khan
2012-05-10 16:34 ` Toshi Kani
2012-05-10 16:55 ` Shuah Khan
2012-05-10 17:41 ` Toshi Kani
2012-05-08 20:12 ` [PATCH v2 4/7] ACPI: Add _OST support for ACPI CPU hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 5/7] ACPI: Add _OST support for ACPI memory hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 6/7] ACPI: Add _OST support for ACPI container hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 7/7] ACPI: Set hotplug _OST support bit to _OSC Toshi Kani
2012-05-09 17:36 ` [PATCH v2 0/7] ACPI: Add _OST support for ACPI hotplug Shuah Khan
2012-05-09 18:44 ` Toshi Kani
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=4FAC5A1E.3090602@gmail.com \
--to=liuj97@gmail.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkhan@gmail.com \
--cc=toshi.kani@hp.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).