From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: Janosch Frank <frankja@linux.ibm.com>,
borntraeger@linux.ibm.com, david@redhat.com, kvm@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v1 2/3] KVM: s390: add stat counter for shadow gmap events
Date: Tue, 9 May 2023 17:14:04 +0200 [thread overview]
Message-ID: <20230509171404.1495e864@p-imbrenda> (raw)
In-Reply-To: <168364406109.331309.632943177292737298@t14-nrb>
On Tue, 09 May 2023 16:54:21 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> Quoting Janosch Frank (2023-05-09 13:59:46)
> [...]
> > > diff --git a/arch/s390/include/asm/kvm_host.h b/arch/s390/include/asm/kvm_host.h
> > > index 3c3fe45085ec..7f70e3bbb44c 100644
> > > --- a/arch/s390/include/asm/kvm_host.h
> > > +++ b/arch/s390/include/asm/kvm_host.h
> > > @@ -777,6 +777,11 @@ struct kvm_vm_stat {
> > > u64 inject_service_signal;
> > > u64 inject_virtio;
> > > u64 aen_forward;
> > > + u64 gmap_shadow_acquire;
> > > + u64 gmap_shadow_r2;
> > > + u64 gmap_shadow_r3;
> > > + u64 gmap_shadow_segment;
> > > + u64 gmap_shadow_page;
> >
> > This needs to be gmap_shadow_pgt and then we need a separate shadow page
> > counter that's beeing incremented in kvm_s390_shadow_fault().
> >
> >
> > I'm wondering if we should name them after the entries to reduce
> > confusion especially when we get huge pages in the future.
> >
> > gmap_shadow_acquire
> > gmap_shadow_r1_te (ptr to r2 table)
> > gmap_shadow_r2_te (ptr to r3 table)
> > gmap_shadow_r3_te (ptr to segment table)
> > gmap_shadow_sg_te (ptr to page table)
> > gmap_shadow_pg_te (single page table entry)
but then why not calling them gmap_shadow_{pte,pmd,pud,p4d,pgd} ?
>
> Yep, right, this was highly confusing to the point where I was also
> confused by it. Will change that, thanks.
next prev parent reply other threads:[~2023-05-09 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 11:11 [PATCH v1 0/3] KVM: s390: add counters for vsie performance Nico Boehr
2023-05-09 11:12 ` [PATCH v1 1/3] KVM: s390: fix space before open parenthesis Nico Boehr
2023-05-09 11:19 ` Claudio Imbrenda
2023-05-09 11:12 ` [PATCH v1 2/3] KVM: s390: add stat counter for shadow gmap events Nico Boehr
2023-05-09 11:43 ` Claudio Imbrenda
2023-05-09 14:53 ` Nico Boehr
2023-05-09 15:17 ` Claudio Imbrenda
2023-05-09 11:59 ` Janosch Frank
2023-05-09 14:54 ` Nico Boehr
2023-05-09 15:14 ` Claudio Imbrenda [this message]
2023-05-10 6:45 ` Janosch Frank
2023-05-09 11:12 ` [PATCH v1 3/3] KVM: s390: add tracepoint in gmap notifier Nico Boehr
2023-05-09 11:48 ` Claudio Imbrenda
2023-05-09 14:54 ` 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=20230509171404.1495e864@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@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