linux-kernel - Re: [RFC PATCH] PCI: Enable pci bridge when it is needed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 27 Apr 2013 10:03:00 +0800
From:	Yijing Wang <wangyijing@...wei.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] PCI: Enable pci bridge when it is needed

On 2013/4/27 9:57, Yinghai Lu wrote:
> On Fri, Apr 26, 2013 at 6:51 PM, Yijing Wang <wangyijing@...wei.com> wrote:
>> I think it's cool! Now we enable bridge in various places, this is a headache.
>>
>> hi, yinghai, in this patch, enable bridges depend on the driver call pci_enable_device() explicitly.
>> I was a little worried If there has some devices don't have some drivers bound, but used by system.
>> like ioapic, these devices maybe implemented as pci device, but no pci drivers bind, also, maybe they
>> won't call pci_enable_device() explicity. So if they are under the pci bridge, no one will enable the bridge
>> for them.
> 
> If there is really that case, we could call pci_enable_device in
> pci_final quirk for
> them.

Hmm, ok, and I tested this patch in my hotplug machine, it looks good.


> 
> Yinghai
> 
> 


-- 
Thanks!
Yijing

--
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/