All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rzvncj@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Handling a MEM_EVENT_REASON_CR3
Date: Wed, 12 Dec 2012 16:16:47 +0200	[thread overview]
Message-ID: <50C891CF.805@gmail.com> (raw)

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

             reply	other threads:[~2012-12-12 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 14:16 Razvan Cojocaru [this message]
2012-12-13 13:22 ` Handling a MEM_EVENT_REASON_CR3 Tim Deegan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50C891CF.805@gmail.com \
    --to=rzvncj@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.