Re: [discuss] Re: x86_64: 2.6.14-rc4 swiotlb broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 19, 2005 at 09:47:02PM +0900, Yasunori Goto wrote:
> > On Tue, 2005-10-18 at 16:22 -0700, Ravikiran G Thirumalai wrote:
> 
> 
> Hmm.....
> How is this patch? This is another way.
> 
> I think that true issue is there is no way for requester to
> specify maxmum address at __alloc_bootmem_core().
> 
> "goal" is just to keep space lower address as much as possible.
> and __alloc_bootmem_core() doesn't care about max address for requester.
> I suppose it is a bit strange. The swiotlb's case is good example
> by it.

This works for me too.  After this patch I see
[  400.495902] Placing software IO TLB between 0x722a000 - 0xb22a000
which means, the new patch is not digging into the 16MB x86_64 DMA area too. 

Linus would you apply this for 2.6.14?  This is the patch which works for
both x86_64 and ia64 boxes.  I limited my approaches not to touch the core
bootmem allocator for 2.6.14,  but that doesn't seem to work for ia64 boxes.  
Fixing the bootmem is the correct approach IMHO.  But in case you feel 
this is too intrusive for 2.6.14, we can whip up an ugly #ifdef CONFIG_X86_64 
patch which patches swiotlb.c only.

Thanks Yasunori-san for the patch, and Alex for testing out all the patches.

Thanks.
Kiran
-
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]
  Powered by Linux