From: Joel Fernandes <joel@joelfernandes.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Zenghui Yu <yuzenghui@huawei.com>,
wanghaibin.wang@huawei.com, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] tracepoint: fix bad trace value in trace_kvm_exit()
Date: Thu, 29 Nov 2018 18:18:42 -0800 [thread overview]
Message-ID: <20181130021842.GA104630@google.com> (raw)
In-Reply-To: <20181128213442.08e90ed4@vmware.local.home>
On Wed, Nov 28, 2018 at 09:34:42PM -0500, Steven Rostedt wrote:
> On Thu, 29 Nov 2018 10:21:55 +0800
> Zenghui Yu <yuzenghui@huawei.com> wrote:
>
> > On 2018/11/28 11:54, Steven Rostedt wrote:
> > > On Wed, 28 Nov 2018 03:35:23 +0000
> > > Zenghui Yu <yuzenghui@huawei.com> wrote:
> > >
> > >> After enabling KVM event tracing, almost all of trace_kvm_exit()'s
> > >> printk shows
> > >>
> > >> "kvm_exit: IRQ: ..."
> > >>
> > >> even if the actual exception_type is NOT IRQ. More specifically,
> > >> trace_kvm_exit() is defined in virt/kvm/arm/trace.h by TRACE_EVENT.
> > >>
> > >> This slight problem may have existed after commit e6753f23d961
> > >> ("tracepoint: Make rcuidle tracepoint callers use SRCU"). There are
> > >> two variables in trace_kvm_exit() and __DO_TRACE() which have the
> > >> same name, *idx*. Thus the actual value of *idx* will be overwritten
> > >> when tracing. Fix it by adding a simple prefix.
> > >
> > > Nice catch! I'll apply it tomorrow and start testing it then.
> >
> > Thanks Steven!
> >
>
> FYI, I renamed your subject to:
>
> tracepoint: Use __idx instead of idx in DO_TRACE macro to make it unique
>
> to make the name more specific to the fix and not the symptom.
>
> Thanks!
Thanks!
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
- Joel
prev parent reply other threads:[~2018-11-30 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 3:35 [PATCH] tracepoint: fix bad trace value in trace_kvm_exit() Zenghui Yu
2018-11-28 3:54 ` Steven Rostedt
2018-11-29 2:21 ` Zenghui Yu
2018-11-29 2:34 ` Steven Rostedt
2018-11-30 2:18 ` Joel Fernandes [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=20181130021842.GA104630@google.com \
--to=joel@joelfernandes.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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.