From: Gavin Shan <gshan@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, paulus@ozlabs.org,
maz@kernel.org, jhogan@kernel.org, drjones@redhat.com,
vkuznets@redhat.com, gshan@redhat.com
Subject: [PATCH 3/3] kvm/arm: Standardize kvm exit reason field
Date: Thu, 12 Dec 2019 13:45:12 +1100 [thread overview]
Message-ID: <20191212024512.39930-4-gshan@redhat.com> (raw)
This standardizes kvm exit reason field name by replacing "esr_ec"
with "exit_reason".
Signed-off-by: Gavin Shan <gshan@redhat.com>
---
virt/kvm/arm/trace.h | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/virt/kvm/arm/trace.h b/virt/kvm/arm/trace.h
index 204d210d01c2..0ac774fd324d 100644
--- a/virt/kvm/arm/trace.h
+++ b/virt/kvm/arm/trace.h
@@ -27,25 +27,27 @@ TRACE_EVENT(kvm_entry,
);
TRACE_EVENT(kvm_exit,
- TP_PROTO(int ret, unsigned int esr_ec, unsigned long vcpu_pc),
- TP_ARGS(ret, esr_ec, vcpu_pc),
+ TP_PROTO(int ret, unsigned int exit_reason, unsigned long vcpu_pc),
+ TP_ARGS(ret, exit_reason, vcpu_pc),
TP_STRUCT__entry(
__field( int, ret )
- __field( unsigned int, esr_ec )
+ __field( unsigned int, exit_reason )
__field( unsigned long, vcpu_pc )
),
TP_fast_assign(
__entry->ret = ARM_EXCEPTION_CODE(ret);
- __entry->esr_ec = ARM_EXCEPTION_IS_TRAP(ret) ? esr_ec : 0;
+ __entry->exit_reason =
+ ARM_EXCEPTION_IS_TRAP(ret) ? exit_reason: 0;
__entry->vcpu_pc = vcpu_pc;
),
TP_printk("%s: HSR_EC: 0x%04x (%s), PC: 0x%08lx",
__print_symbolic(__entry->ret, kvm_arm_exception_type),
- __entry->esr_ec,
- __print_symbolic(__entry->esr_ec, kvm_arm_exception_class),
+ __entry->exit_reason,
+ __print_symbolic(__entry->exit_reason,
+ kvm_arm_exception_class),
__entry->vcpu_pc)
);
--
2.23.0
next reply other threads:[~2019-12-12 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 2:45 Gavin Shan [this message]
2019-12-12 9:23 ` [PATCH 3/3] kvm/arm: Standardize kvm exit reason field Marc Zyngier
2019-12-13 0:50 ` Gavin Shan
2019-12-13 9:47 ` Marc Zyngier
2019-12-13 23:14 ` Gavin Shan
2019-12-16 9:14 ` Vitaly Kuznetsov
2019-12-16 9:35 ` Marc Zyngier
2019-12-17 2:03 ` Gavin Shan
2019-12-17 10:56 ` Paolo Bonzini
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=20191212024512.39930-4-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=drjones@redhat.com \
--cc=jhogan@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=vkuznets@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox