[lkml]   [2005]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC/Patch 0/12] ACPI based root bridge hot-add
On Fri, Mar 18, 2005 at 01:38:57PM -0800, Rajesh Shah wrote:
> Here is a series of patches to support ACPI hot-add of a root
> bridge hierarchy. The added hierarchy may contain other p2p
> bridges and end/leaf I/O devices too. The root bridge itself is
> assumed to have been assigned resource ranges, but the p2p
> bridges and end devices are not required to be initialized by
> firmware. Most of the code changes are to make the existing code
> flows suitable for such a hierarchy of bridges & devices.
> This code supports hot-add on ia64 only for now.It does not yet
> support I/O APIC hot-add, which is needed to make this fully
> functional. The patches are against 2.6.11-mm4 (plus the patch
> needed for ia64 to boot). I've tested to make sure this does not
> break end/leaf device hotplug on the hotplug capable ia64 box I have.

This all looks very good, nice job. I only had one minor comment on the
patches, which I'll reply to directly.

But I did have a few questions:
- This series relys on Mathew's rewrite of the acpiphp driver.
Is that acceptable? Is that patch necessary for your work?
And if so, can you include it in the whole series?
- Does this break the i386 acpiphp functionality?
- Have you tested other pci hotplug systems with this patch
series? Like pci express hotplug, standard pci hotplug,
cardbus, etc?
- Are you wanting the acpi specific patches to go into the tree
through the acpi developers? How about the ia64 specific
- Have the acpi developers agreed with your acpi patches?


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:11    [W:0.082 / U:2.632 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site