On 6/3/06, Ian Campbell <[EMAIL PROTECTED]> wrote:
Jun 3 16:56:05 marvin kernel: Software IO TLB enabled:
Jun 3 16:56:05 marvin kernel: Aperture: 2 megabytes
Jun 3 16:56:05 marvin kernel: Bus range: 0x0000000023a00000 - 0x0000000023c00000
Jun 3 16:56:05 marvin kernel: Kernel range: 0x00000000c08bc000 - 0x00000000c0abc000
Jun 3 16:56:05 marvin kernel: vmalloc area: f4800000-fb3fe000, maxmem 33ffe000
So yes, it is 2M.
Thanks for the hints! I will try on monday and report back.
Sietse
Xen dom0 always uses swiotlb and I think it defaults to a 2M region if
you have <2G RAM and 64M otherwise. There should be a message in dmesg
about it when it initialises.
Jun 3 16:56:05 marvin kernel: Software IO TLB enabled:
Jun 3 16:56:05 marvin kernel: Aperture: 2 megabytes
Jun 3 16:56:05 marvin kernel: Bus range: 0x0000000023a00000 - 0x0000000023c00000
Jun 3 16:56:05 marvin kernel: Kernel range: 0x00000000c08bc000 - 0x00000000c0abc000
Jun 3 16:56:05 marvin kernel: vmalloc area: f4800000-fb3fe000, maxmem 33ffe000
So yes, it is 2M.
IVTV must use a lot of DMA memory since it appears to be running out.
You can increase the amount of space reserved with e.g. swiotlb=32M on
the dom0 kernel command line.
You might also need to restrict the amount of memory given to dom0 in
the first place so there is more left over for DMA buffers. You can do
this by using the dom0_mem Xen command line option:
/*
* dom0_mem:
* If +ve:
* * The specified amount of memory is allocated to domain 0.
* If -ve:
* * All of memory is allocated to domain 0, minus the specified amount.
* If not specified:
* * All of memory is allocated to domain 0, minus 1/16th which is reserved
* for uses such as DMA buffers (the reservation is clamped to 128MB).
*/
Something like dom0_mem=-128M would be a good start I suppose.
Thanks for the hints! I will try on monday and report back.
Sietse
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
