Messages in this thread | | | Date | Mon, 17 Oct 2005 12:02:57 +0200 | From | Muli Ben-Yehuda <> | Subject | Re: x86_64: 2.6.14-rc4 swiotlb broken |
| |
On Mon, Oct 17, 2005 at 02:50:07AM -0700, Andrew Morton wrote: > Ravikiran G Thirumalai <kiran@scalex86.org> wrote: > > > > On x86_64 NUMA boxes, the revert > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6e3254c4e2927c117044a02acf5f5b56e1373053 > > meant that swiotlb gets the IOTLB > > memory from pages over 4G (if mem > 4G), which basically renders swiotlb useless, causing > > breakage with devices not capable of DMA beyond 4G. 2.6.13 was (kinda) not > > broken, although the patch titled "Reverse order of bootmem lists" was > > not in 2.6.13, The reason is commit > > http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6142891a0c0209c91aa4a98f725de0d6e2ed4918 > > was not in 2.6.13, PCI_DMA_BUS_IS_PHYS was 1 when no mmu was present, and the block layer did > > the bouncing, never using swiotlb. I guess the right fix is to make sure > > swiotlb gets the right memory. Here is a patch doing that. Tested on IBM > > x460. I hope the patch is ok for ia64s too. I do not have access to ia64 > > boxen. > > > > This is an ia64 patch - what point was there in testing it on an x460? > > Is something missing here?
x86-64 uses swioltb as well, via arch/ia64 directly. John Linville has a patch to move the swiotlb to lib/swiotlb.c that is waiting in an IA64 for inclusion (post 2.6.14, I guess?)
Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/
- 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/
| |