Messages in this thread | | | Date | Mon, 4 Jun 2007 15:31:50 -0400 | From | Jeff Garzik <> | Subject | Re: [PATCH 5/15] x86-64: Calgary - abstract how we find the iommu_table for a device |
| |
On Mon, Jun 04, 2007 at 10:13:46PM +0300, Muli Ben-Yehuda wrote: > It's already being used in mainline by both NUMA and Calgary (but in > such a way that both work. Magic). Clearly the solution is what we did > for pciseg, have a struct sysdata that is extensible, but those pciseg > bits don't seem any closer to going upstream?
You are missing:
* allocation code in arch/i386/pci/common.c * use of the more-generic pci_iommu() wrapper in Calgary code * ditto in arch/x86_64/kernel/tce.c * pci_sysdata initialization in arch/x86_64/pci/k8-bus.c * definition of pci_sysdata in include/asm-i386/pci.h * bug fix in include/asm-i386/topology.h * definition of pci_sysdata in include/asm-x86_64/pci.h * bug fix in include/asm-x86_64/topology.h
You need to take the obviously relevant, non-PCI-domain code from #pciseg and push it upstream.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |