On Monday 17 October 2005 17:56, Muli Ben-Yehuda wrote:
> On Mon, Oct 17, 2005 at 05:40:56PM +0200, Andi Kleen wrote:
> > First this problem is definitely not critical. AFAIK it only happens on
> > scalex's unreleased machines. Intel NUMA x86 machines are really rare
> > and on AMD it doesn't happen because the swiotlb is not used there.
>
> It's not used by default, but there are cases where it's used and it
> would be a shame to release a major kernel and knowingly break
> them. For example, any setup that used iommu_force or any non-AMD
> x86-64 machine with more than 4GB of memory and only 32-bit capable
> DMA devices.
... but risk breaking other stuff. Unless you can get the ARM and/or IA64
people to do some retesting with the proposed fixes it's quite risky.
Sometimes you have to make compromises before releases.
> Another alternative is to temporarily
> provide a different version of swiotlb_init() for x86-64 and IA64 -
> I can whip up a patch if that's acceptable.
I don't want that.
-Andi
-
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]
