hvmemul_read_cr ends up being called fairly freqently during
emulation; these are generally not necessary for understanding a
trace, and make processing more complicated (because they show up as
extra trace records within a vmexit/entry "arc" that must be
classified).
Leave the trace in write_cr, as any hypothetical writes to CRs *will*
be necessary to understand traces.
Signed-off-by: George Dunlap <george.dunlap@cloud.com>
---
xen/arch/x86/hvm/emulate.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/xen/arch/x86/hvm/emulate.c b/xen/arch/x86/hvm/emulate.c
index 02e378365b..e78f06cf3f 100644
--- a/xen/arch/x86/hvm/emulate.c
+++ b/xen/arch/x86/hvm/emulate.c
@@ -2180,7 +2180,6 @@ static int cf_check hvmemul_read_cr(
case 3:
case 4:
*val = current->arch.hvm.guest_cr[reg];
- TRACE(TRC_HVM_CR_READ64, reg, *val, *val >> 32);
return X86EMUL_OKAY;
default:
break;
--
2.25.1