From: David Hildenbrand <david@redhat.com>
To: Nico Boehr <nrb@linux.ibm.com>,
borntraeger@linux.ibm.com, frankja@linux.ibm.com,
imbrenda@linux.ibm.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 2/2] KVM: s390: add tracepoint in gmap notifier
Date: Thu, 27 Jul 2023 09:41:51 +0200 [thread overview]
Message-ID: <6f8951e2-9ea6-5bad-9c2c-b27d70d57ffe@redhat.com> (raw)
In-Reply-To: <20230510121822.546629-3-nrb@linux.ibm.com>
On 10.05.23 14:18, Nico Boehr wrote:
> The gmap notifier is called for changes in table entries with the
> notifier bit set. To diagnose performance issues, it can be useful to
> see what causes certain changes in the gmap.
>
> Hence, add a tracepoint in the gmap notifier.
>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> ---
> arch/s390/kvm/kvm-s390.c | 2 ++
> arch/s390/kvm/trace-s390.h | 23 +++++++++++++++++++++++
> 2 files changed, 25 insertions(+)
>
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index ded4149e145b..e8476c023b07 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -3982,6 +3982,8 @@ static void kvm_gmap_notifier(struct gmap *gmap, unsigned long start,
> unsigned long prefix;
> unsigned long i;
>
> + trace_kvm_s390_gmap_notifier(start, end, gmap_is_shadow(gmap));
> +
> if (gmap_is_shadow(gmap))
> return;
> if (start >= 1UL << 31)
> diff --git a/arch/s390/kvm/trace-s390.h b/arch/s390/kvm/trace-s390.h
> index 6f0209d45164..5dabd0b64d6e 100644
> --- a/arch/s390/kvm/trace-s390.h
> +++ b/arch/s390/kvm/trace-s390.h
> @@ -333,6 +333,29 @@ TRACE_EVENT(kvm_s390_airq_suppressed,
> __entry->id, __entry->isc)
> );
>
> +/*
> + * Trace point for gmap notifier calls.
> + */
> +TRACE_EVENT(kvm_s390_gmap_notifier,
> + TP_PROTO(unsigned long start, unsigned long end, unsigned int shadow),
> + TP_ARGS(start, end, shadow),
> +
> + TP_STRUCT__entry(
> + __field(unsigned long, start)
> + __field(unsigned long, end)
> + __field(unsigned int, shadow)
> + ),
> +
> + TP_fast_assign(
> + __entry->start = start;
> + __entry->end = end;
> + __entry->shadow = shadow;
> + ),
> +
> + TP_printk("gmap notified (start:0x%lx end:0x%lx shadow:%d)",
> + __entry->start, __entry->end, __entry->shadow)
> + );
> +
>
> #endif /* _TRACE_KVMS390_H */
>
In the context of vsie, I'd have thought you'd be tracing
kvm_s390_vsie_gmap_notifier() instead.
This should work as well, as all notifier are called.
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-07-27 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 12:18 [PATCH v2 0/2] KVM: s390: add counters for vsie performance Nico Boehr
2023-05-10 12:18 ` [PATCH v2 1/2] KVM: s390: add stat counter for shadow gmap events Nico Boehr
2023-07-27 7:37 ` David Hildenbrand
2023-08-01 11:48 ` Nico Boehr
2023-08-01 13:34 ` Janosch Frank
2023-05-10 12:18 ` [PATCH v2 2/2] KVM: s390: add tracepoint in gmap notifier Nico Boehr
2023-07-27 7:41 ` David Hildenbrand [this message]
2023-08-04 9:46 ` Nico Boehr
2023-08-04 9:59 ` David Hildenbrand
2023-07-27 7:24 ` [PATCH v2 0/2] KVM: s390: add counters for vsie performance Nico Boehr
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=6f8951e2-9ea6-5bad-9c2c-b27d70d57ffe@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.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