[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] question about memory mapping and balloon

In the paravirt case, guestos maintain its own mfn which need m2p and p2m ,or xen manage these ? I am confused about how does guestOS maintain its virt-to-physic and physic-to-mach mapping ,in the linux ,there is only v2p mapping, how does guestOS maintain its p2m mapping ,and when a virt address is put into a mmu, does cpu hardware convert virt-addr into machine address or guest's phyiscal address?

another one
does xen in hvm case support balloon for modifying the vm memory size or not?

I am confused about it

could you help me
Thanks in advance

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.