Some corrections to the preamble.
The large amount of text is due to the nature of the
problem and the discussion it engendered on the lkml.
Should say:
The large amount of text in the explanation below is due to
the nature of the problem and the discussion engendered on
lkml by my first submission.
This patch-set detects the problem by comparing an MMCONFIG
read to a Legacy PCI config read of the vendor/device dword
of every device discovered during the PCI probing sequence.
Actually, the patch doesn't do a pci config read of EVERY device
discovered on every bus. Only on buses above a number defined
by PCI_MMCFG_MAX_CHECK_BUS and whose parent bus's pci_bus.ops
field points to pci_root_ops, which are mmconfig access routines
in systems in which mmconfig is the default mechanism.
In such cases where the parent bus pci_bus.ops field points
to pci_legacy_ops, the current bus does not need to be probed,
since its own pci_bus.ops field will inherit the pointer to
pci_legacy_ops from its parent.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
