From mboxrd@z Thu Jan 1 00:00:00 1970 From: tgh Subject: question about memory mapping and balloon Date: Tue, 27 Mar 2007 10:34:39 +0800 Message-ID: <460882BF.7000804@ncic.ac.cn> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Xen Devel List List-Id: xen-devel@lists.xenproject.org hi 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