From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
mdontu <mdontu@bitdefender.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: [PATCH RFC V2 0/6] Basic guest memory introspection support
Date: Fri, 11 Jul 2014 18:44:21 +0300 [thread overview]
Message-ID: <53C00655.7030106@bitdefender.com> (raw)
Hello,
First of all, thank you all for your reviews! Based on what we've
discussed, a new series follows.
Changes since V1:
- Removed, for the time being, the Linux-borrowed code for
computing instruction length.
- Removed the code that attempted to get around emulator limitations
by setting the 'accessed' and 'dirty' bits and re-executing
problematic instructions.
- Skipped the "[PATCH RFC 9/9] mm: mark pages that have their
permissions controlled by a domain" patch, hopefully this has
been fixed in Xen 4.5.
- Took out the trivial C++ patch (previously "[PATCH RFC 4/9]
xenctrl: Make the headers C++ friendly"), also posted
separately and hopefully scheduled for inclusion soon.
- Removed code redundancy.
- Addressed discussed issues (in the code itself, and patch
descriptions - please see individual patches for details).
Patches:
xen: Handle resumed instruction based on previous mem_event reply
xen, libxc: Request page fault injection via libxc
xen: Support for VMCALL mem_events
xen: Force-enable relevant MSR events; optimize the number of sent MSR
events
xen: Optimize introspection access to guest state
xen: Emulate with no writes
Thanks,
Razvan Cojocaru
reply other threads:[~2014-07-11 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53C00655.7030106@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=mdontu@bitdefender.com \
--cc=tim@xen.org \
--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.