[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51072EDA.2000704@huawei.com>
Date: Tue, 29 Jan 2013 10:07:22 +0800
From: Jiang Liu <jiang.liu@...wei.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Jiang Liu <liuj97@...il.com>,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
Yijing Wang <wangyijing@...wei.com>,
<linux-kernel@...r.kernel.org>, <linux-pci@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Toshi Kani <toshi.kani@...com>,
Myron Stowe <myron.stowe@...hat.com>
Subject: Re: [RFC PATCH v5 4/8] ACPI, PCI: avoid building pci_slot as module
On 2013-1-29 6:58, Yinghai Lu wrote:
> On Mon, Jan 28, 2013 at 2:14 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>>
>> CONFIG_ACPI_PCI_SLOT=y in RHEL6, so evidently they have this problem.
>
> oh, I only checked opensuse that has that set to m.
>
>>
>> Asking users to edit module.conf by hand is not a solution, just like
>> asking users to boot with a command line option is not a solution.
>> That sort of stuff is fine for a hobbyist OS intended only for techie
>> geeks. It's not fine for Linux.
>
> not sure. add something in command line or conf files.
> but recompile kernel is another story.
>
>>
>> If you would give a concrete example of the ACPI namespace info and
>> device config, hotplug sequence, etc., required to show the problem,
>> we could have a useful discussion about ways to fix it. But if all
>> you have is FUD about "this might break and users won't have the
>> ability to edit modules.conf," that doesn't help me see why this patch
>> is a bad idea.
>
> Never mind, We should save your bandwidth to more patches.
Hi Yinghai,
Could we use quirk to auto-disable PCIe native hotplug for
problematic platforms?
Regards!
Gerry
>
> Yinghai
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists