This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Xen Kernel (3.0.2) breaks b44 module

On 12 May 2006, at 10:15, Jan Beulich wrote:

I agree, but this wouldn't help this specific case, as the driver also (and mostly) uses pci_map_single on skb->data, which ends up in swiotlb. Since swiotlb does its allocation and range restriction during init, adjusting things here would likely be more complicated (or cost performance, if one wanted to further restrict the range upon use when

When we support more flexible allocation in Xen, we'll fix up the swiotlb to automatically try to grab some lower memory and/or allow the address mask for the physical memory in the swiotlb to be specified on the kernel command line.

It sounds like 30-bit-addressable memory will be a good thing to try for automatically at init. I'd thought that 31-bit was really as bad as it got (except for old ISA-ish hardware with 24-bit limitations, which we'll never support).

 -- Keir

Xen-devel mailing list