All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Ladi Prosek <lprosek@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: trace events: update list of exit reasons
Date: Thu, 14 Sep 2017 20:07:37 +0200	[thread overview]
Message-ID: <20170914180733.GC23415@flask> (raw)
In-Reply-To: <20170914120646.49139c2a.cohuck@redhat.com>

2017-09-14 12:06+0200, Cornelia Huck:
> On Thu, 14 Sep 2017 11:50:07 +0200
> Ladi Prosek <lprosek@redhat.com> wrote:
> 
>> Adding entries for exit reasons 23 - 27:
>> 
>>   KVM_EXIT_EPR
>>   KVM_EXIT_SYSTEM_EVENT
>>   KVM_EXIT_S390_STSI
>>   KVM_EXIT_IOAPIC_EOI
>>   KVM_EXIT_HYPERV
>> 
>> Signed-off-by: Ladi Prosek <lprosek@redhat.com>
>> ---
>>  include/trace/events/kvm.h | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>> 
>> diff --git a/include/trace/events/kvm.h b/include/trace/events/kvm.h
>> index 8ade3eb..dcffedf 100644
>> --- a/include/trace/events/kvm.h
>> +++ b/include/trace/events/kvm.h
>> @@ -14,7 +14,9 @@
>>  	ERSN(SHUTDOWN), ERSN(FAIL_ENTRY), ERSN(INTR), ERSN(SET_TPR),	\
>>  	ERSN(TPR_ACCESS), ERSN(S390_SIEIC), ERSN(S390_RESET), ERSN(DCR),\
>>  	ERSN(NMI), ERSN(INTERNAL_ERROR), ERSN(OSI), ERSN(PAPR_HCALL),	\
>> -	ERSN(S390_UCONTROL), ERSN(WATCHDOG), ERSN(S390_TSCH)
>> +	ERSN(S390_UCONTROL), ERSN(WATCHDOG), ERSN(S390_TSCH), ERSN(EPR),\
>> +	ERSN(SYSTEM_EVENT), ERSN(S390_STSI), ERSN(IOAPIC_EOI),          \
>> +	ERSN(HYPERV)
>>  
>>  TRACE_EVENT(kvm_userspace_exit,
>>  	    TP_PROTO(__u32 reason, int errno),

Applied, thanks.

> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> 
> /me wonders whether there is a way to avoid them running out of sync...

If we do not want to generate it with an external script, I think the
simplest is to have a separate file that looks like

  #define kvm_exit_reasons \
    KVM_EXIT(UNKNOWN, 0), \
    KVM_EXIT(EXCEPTION, 1), \
    ...
    KVM_EXIT(HYPERV, 27) \

and include it from both places.  The current exit definitions would be

  #define KVM_EXIT(reason, code)
  	KVM_EXIT_ ## reason = code

  #include <the/magic/file>
  
  enum {
  	kvm_exit_reasons
  };

  #undef kvm_exit_reasons

and the trace

  #define KVM_EXIT(reason, code)
  	{ code, "KVM_EXIT_" # reason }
  #include <the/magic/file>

  ...

  	__print_symbolic(__entry->reason, kvm_exit_reasons),

  ...

  #undef kvm_exit_reasons

(Would also work with just "KVM_EXIT(UNKNOWN), ..." and small tweaks.)

> but otoh, not so many exit reasons are being added anyway.

Yes. :)

  reply	other threads:[~2017-09-14 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14  9:50 [PATCH] KVM: trace events: update list of exit reasons Ladi Prosek
2017-09-14 10:06 ` Cornelia Huck
2017-09-14 18:07   ` Radim Krčmář [this message]
2017-09-15  7:30     ` Cornelia Huck
2017-09-15 10:20       ` Paolo Bonzini
2017-09-15 11:17     ` Ladi Prosek
2017-09-15 11:27 ` Paolo Bonzini

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=20170914180733.GC23415@flask \
    --to=rkrcmar@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lprosek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.