[Xen-changelog] [xen-unstable] [HVM] Currently in xentrace, MMIO is handled just like other page faults. The

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 34ba512b2d64cb8b7783e89f9351ccd3da702332
# Parent  078c08dc4b0a8c49943f954bf9dcbd62df203d79
[HVM] Currently in xentrace, MMIO is handled just like other page faults. The
tracing parameters are error code and the guest virtual address.
However, if we are to analyze MMIO, tracing gpa makes more sense.

This small pactch replaces the va with gpa when tracing MMIO.

Signed-off-by: Qing He <qing.he@xxxxxxxxx>
---
 xen/arch/x86/hvm/vmx/vmx.c |    2 ++
 1 files changed, 2 insertions(+)

diff -r 078c08dc4b0a -r 34ba512b2d64 xen/arch/x86/hvm/vmx/vmx.c
--- a/xen/arch/x86/hvm/vmx/vmx.c        Fri Jul 14 14:01:25 2006 +0100
+++ b/xen/arch/x86/hvm/vmx/vmx.c        Fri Jul 14 14:02:59 2006 +0100
@@ -811,6 +811,8 @@ static int vmx_do_page_fault(unsigned lo
             return 1;
         }
         TRACE_VMEXIT (2,2);
+        /* in the case of MMIO, we are more interested in gpa than in va */
+        TRACE_VMEXIT (4,gpa);
         handle_mmio(va, gpa);
         return 1;
     }

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