From mboxrd@z Thu Jan  1 00:00:00 1970
From: Razvan Cojocaru <rzvncj@gmail.com>
Subject: Handling a MEM_EVENT_REASON_CR3
Date: Wed, 12 Dec 2012 16:16:47 +0200
Message-ID: <50C891CF.805@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Hello,

a few questions about receiving a MEM_EVENT_REASON_CR3 even in dom0 
userspace:

1. If I call

xc_set_hvm_param(xci, domain_id,
                  HVM_PARAM_MEMORY_EVENT_CR3,
                  HVMPME_onchangeonly);

that only triggers a CR3 event if the new value that the guest writes to 
CR3 is different from the existing value, is that assumption correct?

2. mem_event.h says that if "CR3 was hit: gfn is CR3 value". I'm 
assuming that gfn is the _new_ value, and that the old value is 
unavailable, is that also correct?

3. Is it possible to, upon intercepting the CR3 write, write a 
_different_ value to CR3, instead of gfn?

Thanks,
Razvan Cojocaru