From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Fabiano Rosas <farosas@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org
Subject: Re: [PATCH] target/ppc: Improve KVM hypercall trace
Date: Wed, 20 Apr 2022 16:12:52 -0300 [thread overview]
Message-ID: <2e62d048-1635-ba62-022b-ce3b30ac6290@gmail.com> (raw)
In-Reply-To: <20220325223316.276494-1-farosas@linux.ibm.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 3/25/22 19:33, Fabiano Rosas wrote:
> Before:
>
> kvm_handle_papr_hcall handle PAPR hypercall
> kvm_handle_papr_hcall handle PAPR hypercall
> kvm_handle_papr_hcall handle PAPR hypercall
> kvm_handle_papr_hcall handle PAPR hypercall
> kvm_handle_papr_hcall handle PAPR hypercall
> kvm_handle_papr_hcall handle PAPR hypercall
>
> After:
>
> kvm_handle_papr_hcall 0x3a8
> kvm_handle_papr_hcall 0x3ac
> kvm_handle_papr_hcall 0x108
> kvm_handle_papr_hcall 0x104
> kvm_handle_papr_hcall 0x104
> kvm_handle_papr_hcall 0x108
>
> Signed-off-by: Fabiano Rosas <farosas@linux.ibm.com>
> ---
> target/ppc/kvm.c | 2 +-
> target/ppc/trace-events | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
> index dc93b99189..a490e886ea 100644
> --- a/target/ppc/kvm.c
> +++ b/target/ppc/kvm.c
> @@ -1681,7 +1681,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)
> break;
> #if defined(TARGET_PPC64)
> case KVM_EXIT_PAPR_HCALL:
> - trace_kvm_handle_papr_hcall();
> + trace_kvm_handle_papr_hcall(run->papr_hcall.nr);
> run->papr_hcall.ret = spapr_hypercall(cpu,
> run->papr_hcall.nr,
> run->papr_hcall.args);
> diff --git a/target/ppc/trace-events b/target/ppc/trace-events
> index 53b107f56e..a79f1b4370 100644
> --- a/target/ppc/trace-events
> +++ b/target/ppc/trace-events
> @@ -23,7 +23,7 @@ kvm_failed_get_vpa(void) "Warning: Unable to get VPA information from KVM"
> kvm_handle_dcr_write(void) "handle dcr write"
> kvm_handle_dcr_read(void) "handle dcr read"
> kvm_handle_halt(void) "handle halt"
> -kvm_handle_papr_hcall(void) "handle PAPR hypercall"
> +kvm_handle_papr_hcall(uint64_t hcall) "0x%" PRIx64
> kvm_handle_epr(void) "handle epr"
> kvm_handle_watchdog_expiry(void) "handle watchdog expiry"
> kvm_handle_debug_exception(void) "handle debug exception"
prev parent reply other threads:[~2022-04-20 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 22:33 [PATCH] target/ppc: Improve KVM hypercall trace Fabiano Rosas
2022-03-26 2:57 ` Richard Henderson
2022-03-28 21:52 ` Daniel Henrique Barboza
2022-04-20 19:12 ` Daniel Henrique Barboza [this message]
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=2e62d048-1635-ba62-022b-ce3b30ac6290@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=farosas@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).