From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
"Cornelia Huck" <cornelia.huck@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
David Hildenbrand <dahi@linux.vnet.ibm.com>,
Wanpeng Li <kernellwp@gmail.com>,
David Matlack <dmatlack@google.com>
Subject: Re: [PATCH 1/1] KVM: halt_polling: provide a way to qualify wakeups during poll
Date: Tue, 3 May 2016 20:12:00 +0200 [thread overview]
Message-ID: <5728E9F0.1090705@de.ibm.com> (raw)
In-Reply-To: <20160503150356.GE30059@potion>
On 05/03/2016 05:03 PM, Radim Krčmář wrote:
> 2016-05-03 14:56+0200, Cornelia Huck:
>> On Tue, 3 May 2016 14:37:21 +0200
>> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>>> diff --git a/include/trace/events/kvm.h b/include/trace/events/kvm.h
>>> index aa69253..92e6fd6 100644
>>> --- a/include/trace/events/kvm.h
>>> +++ b/include/trace/events/kvm.h
>>> @@ -38,22 +38,25 @@ TRACE_EVENT(kvm_userspace_exit,
>>> );
>>>
>>> TRACE_EVENT(kvm_vcpu_wakeup,
>>> - TP_PROTO(__u64 ns, bool waited),
>>> - TP_ARGS(ns, waited),
>>> + TP_PROTO(__u64 ns, bool waited, bool tuned),
>>> + TP_ARGS(ns, waited, tuned),
>>>
>>> TP_STRUCT__entry(
>>> __field( __u64, ns )
>>> __field( bool, waited )
>>> + __field( bool, tuned )
>>> ),
>>>
>>> TP_fast_assign(
>>> __entry->ns = ns;
>>> __entry->waited = waited;
>>> + __entry->tuned = tuned;
>>> ),
>>>
>>> - TP_printk("%s time %lld ns",
>>> + TP_printk("%s time %lld ns, polling %s",
>>> __entry->waited ? "wait" : "poll",
>>> - __entry->ns)
>>> + __entry->ns,
>>> + __entry->tuned ? "changed" : "unchanged")
>>
>> I think "changed"/"unchanged" is a bit misleading here, as we do adjust
>> the intervall if we had an invalid poll... but it's hard to find a
>> suitable text here.
>>
>> Just print "poll interval tuned" if we were (a) polling to begin with,
>> (b) the poll was valid and (c) the interval was actually changed and
>> print "invalid poll" if that's what happened? Or is that overkill?
>
> Just renaming to valid/invalid is fine, IMO, the state of polling is
> static and interval change can be read from other traces.
>
> I think that having "no_tuning" counter, "unchanged" trace and "invalid"
> in source names obscures the logical connection; doesn't "invalid" fit
> them all?
>
Yes, will change tracing into
__entry->valid ? "valid" : "invalid")
and halt_poll_no_tuning --> halt_poll_invalid
That seems to be in line with the remaining parts of the patch.
Christian
next prev parent reply other threads:[~2016-05-03 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 12:37 [PATCH v2] KVM: halt_polling: provide a way to qualify wakeups during poll Christian Borntraeger
2016-05-03 12:37 ` [PATCH 1/1] " Christian Borntraeger
2016-05-03 12:41 ` David Hildenbrand
2016-05-03 12:56 ` Cornelia Huck
2016-05-03 15:03 ` Radim Krčmář
2016-05-03 18:12 ` Christian Borntraeger [this message]
2016-05-04 6:22 ` Cornelia Huck
2016-05-03 15:09 ` Radim Krčmář
2016-05-04 7:50 ` Christian Borntraeger
2016-05-04 8:05 ` Cornelia Huck
2016-05-13 10:18 ` Christian Borntraeger
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=5728E9F0.1090705@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=dmatlack@google.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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