Subject: Xen3 physical memory map/location for dom0
To: None <port-xen@netbsd.org>
From: Daniel Carosone <dan@geek.com.au>
List: port-xen
Date: 11/09/2006 14:55:48
--R85i2aFa0BIOEKaC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
My laptop has a bce(4) onboard NIC, which annoyingly is only usable
with DMA to physical addresses <1G.
I had hoped that, when running Xen, limiting dom0 to less than this
quantity would be enough - but it seems that the dom0 builder
allocates the domain's physical pages from the top down.
I haven't found any clues in xen documentation about way to alter this
(like a flag on the xen grub commmand line). I *can* make bce0 work
by limiting xen to 1g of memory, but that's not really the desired
solution longer term.
Is it something that can be influenced by the ELF headers of the dom0
kernel? I know there were some changes recently (as part of the 3.0.3
support) to load addresses and other possibly promising parameters..
Any other clues?
--
Dan.
--R85i2aFa0BIOEKaC
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)
iD8DBQFFUqbEEAVxvV4N66cRAiw3AJ9dJHwoyIH94Lto2stD7VYD4KbqwgCfV1HW
TVXBHPPPaotKk4iu8JyXsZM=
=ZlN5
-----END PGP SIGNATURE-----
--R85i2aFa0BIOEKaC--