Re: [discuss] Re: Please pull x86-64 bug fixes
- From: Andi Kleen <ak@xxxxxxx>
- Date: Mon, 16 Oct 2006 14:21:25 +0200
On Friday 06 October 2006 13:14, Alan Cox wrote:
Ar Iau, 2006-10-05 am 23:44 +0200, ysgrifennodd Andi Kleen:
I think we had that argument before. IMHO such messages are completely
useless. Hangs are not acceptable no matter what messages are printed
before.
Oh so you plan to fix the iommu/aacraid problem you always said you
wouldn't fix ?
They don't cause hangs, just IO errors (or panics if you configure
iommu debugging)
Actually I plan to fix this one, but it will require more work.
Basically the plan is to make the current dma zone variable sized
and get rid of all GFP_DMA allocations. Merge the current soft iommu
with that new dma allocator. Then make sure all allocations
that need such low dma use a mask argument to some allocator.
Then we can have a option to configure the size of the dma low zone.
Users of broken hardware just configure a larger size.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Please pull x86-64 bug fixes
- From: Andi Kleen
- Re: [discuss] Re: Please pull x86-64 bug fixes
- From: Andi Kleen
- Re: [discuss] Re: Please pull x86-64 bug fixes
- From: Alan Cox
- Please pull x86-64 bug fixes
- Prev by Date: Re: [PATCH 2.6.18 RFC] mmc: Add support for mmc v4 wide-bus modes
- Next by Date: Hardware random intel_rng broken in x86_64 mode on 2.6.18
- Previous by thread: Re: [discuss] Re: Please pull x86-64 bug fixes
- Next by thread: Re: Please pull x86-64 bug fixes
- Index(es):
Relevant Pages
|
