From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xensource.com
Cc: andres@gridcentric.ca, keir.xen@gmail.com, tim@xen.org,
JBeulich@suse.com, adin@gridcentric.ca
Subject: [PATCH 0 of 3] Mem access improvements and new type
Date: Thu, 01 Dec 2011 14:24:56 -0500 [thread overview]
Message-ID: <patchbomb.1322767496@xdev.gridcentric.ca> (raw)
We improve the handling of hap faults when both type and access
restrictions are present.
We also add a new p2m access type, n2rwx. It allows for implement a "log
access" mode in the hypervisor, aking to log dirty but for all types of
accesses. Faults caused by this access mode automatically promote the
access rights of the ofending p2m entry, place the event in the ring, and
let the vcpu keep on executing.
Repost after feedback from Tim Deegan.
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Signed-off-by: Adin Scannell <adin@scannell.ca>
xen/arch/x86/hvm/hvm.c | 14 +++++++++-----
xen/arch/x86/hvm/hvm.c | 20 +++++++++++++++-----
xen/arch/x86/mm/p2m.c | 8 +++++---
xen/include/asm-x86/p2m.h | 9 +++++----
xen/arch/x86/hvm/hvm.c | 1 +
xen/arch/x86/mm/p2m-ept.c | 1 +
xen/arch/x86/mm/p2m.c | 30 +++++++++++++++++++++---------
xen/include/asm-x86/p2m.h | 3 +++
xen/include/public/hvm/hvm_op.h | 3 +++
9 files changed, 63 insertions(+), 26 deletions(-)
next reply other threads:[~2011-12-01 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 19:24 Andres Lagar-Cavilla [this message]
2011-12-01 19:24 ` [PATCH 1 of 3] Improve handling of nested page faults Andres Lagar-Cavilla
2011-12-01 19:24 ` [PATCH 2 of 3] x86/mm: When mem event automatically promotes access rights, let other subsystems know Andres Lagar-Cavilla
2011-12-01 19:24 ` [PATCH 3 of 3] x86/mm: New mem access type to log access Andres Lagar-Cavilla
2011-12-06 20:38 ` [PATCH 0 of 3] Mem access improvements and new type Tim Deegan
2011-12-06 21:05 ` Andres Lagar-Cavilla
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=patchbomb.1322767496@xdev.gridcentric.ca \
--to=andres@lagarcavilla.org \
--cc=JBeulich@suse.com \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.com \
/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.