From: Avi Kivity <avi@redhat.com>
To: "Sanagi, Koki" <sanagi.koki@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"fweisbec@gmail.com" <fweisbec@gmail.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: [PATCH] kvm/ftrace: change the diplaying format of vector in trace_msi_set_irq
Date: Thu, 18 Oct 2012 16:49:00 +0200 [thread overview]
Message-ID: <508016DC.1040509@redhat.com> (raw)
In-Reply-To: <F6CB40852BC6EF489E0AA83EFF537F4708724889@G01JPEXMBYT04>
On 10/12/2012 02:03 AM, Sanagi, Koki wrote:
> This patch changes the way to diplay the vector in trace_msi_set_irq from %x to
> %u. Currently, it mismatches another output of ftrace such as kvm_msi_set_irq
> and kvm_inj_virq which uses %u.
>
> Signed-off-by: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
> ---
> include/trace/events/kvm.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/trace/events/kvm.h b/include/trace/events/kvm.h
> index 7ef9e75..0a83632 100644
> --- a/include/trace/events/kvm.h
> +++ b/include/trace/events/kvm.h
> @@ -109,7 +109,7 @@ TRACE_EVENT(kvm_msi_set_irq,
> __entry->data = data;
> ),
>
> - TP_printk("dst %u vec %x (%s|%s|%s%s)",
> + TP_printk("dst %u vec %u (%s|%s|%s%s)",
> (u8)(__entry->address >> 12), (u8)__entry->data,
> __print_symbolic((__entry->data >> 8 & 0x7), kvm_deliver_mode),
> (__entry->address & (1<<2)) ? "logical" : "physical",
Changing them all to %02x is probably better. For example, writes to
APIC_ICR will be shown as hex, with the vector in the low order 8 bits,
so it will be easier to match them if they are all in hex.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-10-18 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 0:03 [PATCH] kvm/ftrace: change the diplaying format of vector in trace_msi_set_irq Sanagi, Koki
2012-10-18 14:49 ` Avi Kivity [this message]
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=508016DC.1040509@redhat.com \
--to=avi@redhat.com \
--cc=fweisbec@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sanagi.koki@jp.fujitsu.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