On 07/30/2009 02:52 AM, Cam Macdonell wrote:
You need a variant of qemu_ram_alloc() that accepts an fd and offset
and mmaps that. A less intrusive, but uglier, alternative is to call
qemu_ram_alloc() and them mmap(MAP_FIXED) on top of that.
Hi Avi,
I noticed that the region of memory being allocated for shared memory
using qemu_ram_alloc gets added to the total RAM of the system
(according to /proc/meminfo). I'm wondering if this is normal/OK
since memory for the shared memory device (and similarly VGA RAM) is
not intended to be used as regular RAM.
qemu_ram_alloc() and the guets /proc/meminfo are totally disconnected.
I don't understand how that happened.
Should memory of devices be reported as part of MemTotal or is
something wrong in my use of qemu_ram_alloc()?
You can call qemu_ram_alloc() all you like. Guest memory is determined
by the e820 map, which is in turn determined by the -m parameter.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
