linux-kernel - Re: [PATCH] Add option to passively listen for PCIE hotplug events

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081104023837.GA12165@srcf.ucam.org>
Date:	Tue, 4 Nov 2008 02:38:37 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
Cc:	linux-pci@...r.kernel.org, kristen.c.accardi@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add option to passively listen for PCIE hotplug events

On Tue, Nov 04, 2008 at 11:29:43AM +0900, Kenji Kaneshige wrote:
> Matthew Garrett wrote:
> >What do you mean by "not work properly"? The hardware we've tested with 
> >fires events even without an OSHP method being present. That's the case 
> >we're trying to deal with.
> >
> 
> Because the explanation of PCI Express Native Hot Plug control bit in
> _OSC return value in PCI firmware spec says
> 
> "... If firmware allows the operating system control of this feature,
> then in the context of the _OSC method, it must ensure that all hot
> plug events are routed to device interrupts as described in the PCI
> Express Base Specification. ..."
> 
> My understanding is that it is not ensured that all hot plug events
> are routed to device interrupts, if hotplug control is not granted.

My understanding is that in the worst case the hardware/firmware won't 
give us any events - that's basically equivalent to not having the 
driver loaded at all. On hardware that gives us the events anyway, we 
get some extra functionality.

Thanks for the feedback!
-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/