linux-kernel - Q: state of pci express hotplug

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

Message-ID: <m1fxj06js8.fsf@fess.ebiederm.org>
Date:	Fri, 30 Jan 2009 23:01:43 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	linux-pci@...r.kernel.org
Cc:	jbarnes@...tuousgeek.org, Alex Chiang <achiang@...com>,
	djwong@...ibm.com, Trent Piepho <xyzzy@...akeasy.org>,
	<linux-kernel@...r.kernel.org>
Subject: Q: state of pci express hotplug

Trying to use the current pciehp code, on real hardware in an 
interesting topology (more later) I'm not finding it very satisfactory
at all.  I am up to at least three show stopper bugs and the code
is not doing what I really need it to do, so I am looking at a significant
rewrite patch effort to make this code usable.

Am I unique in thinking there is a lot that needs to be done?
Is there current work in progress to make the pci hotplug work better?

I would like to avoid duplicate work if I can.

Eric

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