From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Vm_event memory introspection helpers Date: Mon, 15 Jun 2015 12:03:24 +0300 Message-ID: <1434359007-9302-1-git-send-email-rcojocaru@bitdefender.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org Cc: kevin.tian@intel.com, keir@xen.org, eddie.dong@intel.com, stefano.stabellini@eu.citrix.com, jun.nakajima@intel.com, andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com, tim@xen.org, Aravind.Gopalakrishnan@amd.com, jbeulich@suse.com, wei.liu2@citrix.com, boris.ostrovsky@oracle.com, suravee.suthikulpanit@amd.com, ian.campbell@citrix.com List-Id: xen-devel@lists.xenproject.org Hello, Since the first version of the series, which consisted of five patches, the following major changes have happened: 1. The first patch in the previous series has already been accepted, under the name "xen/vm_event: Clean up control-register-write vm_events and add XCR0 event". The patch was "xen/vm_event: Added support for XSETBV events" - the XCR0 is the previously-named XSETBV event. 2. It has been decided that having a single DENY vm_event flag that applies to both CR and MSR writes is not an outlandish idea, and as such the last patch (patch 5) from the previous series has been removed, and the CR0, CR3 and CR4 write events are now being sent as pre-write events, to be denied the same way as the MSR writes are, in patch #3. So the current version now went from 5 patches to 3: [PATCH V2 1/3] xen/vm_access: Support for memory-content hiding [PATCH V2 2/3] xen/vm_event: Support for guest-requested events [PATCH V2 3/3] xen/vm_event: Deny register writes if refused by vm_event reply. Thanks, Razvan Cojocaru