This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Question on p2m table

To: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Question on p2m table
From: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
Date: Tue, 31 May 2011 00:15:54 +0800
Delivery-date: Mon, 30 May 2011 11:03:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <SNT0-MC4-F36Ccpzvqk001553a4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <SNT0-MC4-F36Ccpzvqk001553a4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
  Question might be simple but really confused me a long time.
  In my assumption, during VM running, the CPU sees the guest code instruction,
so when it want to asscess memory, it sees the guest virtual adress(GVA), so it need to
first translate to guest physical adress(GPA), and then host physical adress(HPA), and finally
access the real memory address.
Since GPA are always needs to translated to HPA, and p2m table only accessable in Xen for
HVM guest, does this mean every memory access will need VMExit to Xen?
many thanks.
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>