public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	borntraeger@linux.ibm.com, imbrenda@linux.ibm.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 1/2] KVM: s390: add stat counter for shadow gmap events
Date: Tue, 1 Aug 2023 15:34:44 +0200	[thread overview]
Message-ID: <b5c1b495-cd59-e42e-a902-50f5fef0fad0@linux.ibm.com> (raw)
In-Reply-To: <169089049005.9734.15826596498609647664@t14-nrb>

On 8/1/23 13:48, Nico Boehr wrote:
> Quoting David Hildenbrand (2023-07-27 09:37:21)
> [...]
>>> diff --git a/arch/s390/include/asm/kvm_host.h b/arch/s390/include/asm/kvm_host.h
>>> index 2bbc3d54959d..d35e03e82d3d 100644
>>> --- a/arch/s390/include/asm/kvm_host.h
>>> +++ b/arch/s390/include/asm/kvm_host.h
>>> @@ -777,6 +777,12 @@ struct kvm_vm_stat {
>>>        u64 inject_service_signal;
>>>        u64 inject_virtio;
>>>        u64 aen_forward;
>>> +     u64 gmap_shadow_acquire;
>>> +     u64 gmap_shadow_r1_te;
>>> +     u64 gmap_shadow_r2_te;
>>> +     u64 gmap_shadow_r3_te;
>>> +     u64 gmap_shadow_sg_te;
>>> +     u64 gmap_shadow_pg_te;
>>
>> Is "te" supposed to stand for "table entry" ?
> 
> Yes.
> 
>> If so, I'd suggest to just call this gmap_shadow_pg_entry etc.
> 
> Janosch, since you suggested the current naming, are you OK with _entry?

Sure

> 
> [...]
>>> diff --git a/arch/s390/kvm/vsie.c b/arch/s390/kvm/vsie.c
>>> index 8d6b765abf29..beb3be037722 100644
>>> --- a/arch/s390/kvm/vsie.c
>>> +++ b/arch/s390/kvm/vsie.c
>>> @@ -1221,6 +1221,7 @@ static int acquire_gmap_shadow(struct kvm_vcpu *vcpu,
>>>        if (IS_ERR(gmap))
>>>                return PTR_ERR(gmap);
>>>        gmap->private = vcpu->kvm;
>>> +     vcpu->kvm->stat.gmap_shadow_acquire++;
>>
>>
>> Do you rather want to have events for
>>
>> gmap_shadow_reuse (if gmap_shadow_valid() succeeded in that function)
>> gmap_shadow_create (if we have to create a new one via gmap_shadow)
>>
>> ?
> 
> Yeah, good suggestion. I'll add that.


  reply	other threads:[~2023-08-01 13:34 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 [this message]
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
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=b5c1b495-cd59-e42e-a902-50f5fef0fad0@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.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