[Xen-changelog] [xen master] x86/mem_event: fix regression affecting CR0 memory events

[patchbot@xxxxxxx]

commit 5d570c1d0274cac3b333ef378af3325b3b69905e
Author:     Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx>
AuthorDate: Wed Jul 23 18:05:11 2014 +0200
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Wed Jul 23 18:05:11 2014 +0200

    x86/mem_event: fix regression affecting CR0 memory events
    
    This is a patch repairing a regression in code previously functional in 
4.1.x.
    It appears that, during some refactoring work, call to hvm_memory_event_cr0 
was lost.
    
    This function was originally called in mov_to_cr() of vmx.c, but the commit
    http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the
    original code into generic functions up a level in hvm.c, dropping the call
    in the process.
    
    The same issue affected the CR3 and CR4 events, which were fixed in patch
    http://xenbits.xensource.com/hg/xen-unstable.hg/rev/7ab899e46347.
    
    Signed-off-by: Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx>
    Reviewed-by: Tim Deegan <tim@xxxxxxx>
---
 xen/arch/x86/hvm/hvm.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
index db54814..fea6d05 100644
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -3200,6 +3200,7 @@ int hvm_set_cr0(unsigned long value)
         hvm_funcs.handle_cd(v, value);
 
     hvm_update_cr(v, 0, value);
+    hvm_memory_event_cr0(value, old_value);
 
     if ( (value ^ old_value) & X86_CR0_PG ) {
         if ( !nestedhvm_vmswitch_in_progress(v) && 
nestedhvm_vcpu_in_guestmode(v) )
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog