Linux USB
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org,
	Tzvetomir Stoyanov <tstoyanov@vmware.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>
Subject: Re: [PATCH] xhci: Do not open code __print_symbolic() in xhci trace events
Date: Wed, 19 Feb 2020 11:20:08 +0200	[thread overview]
Message-ID: <c25679c6-de22-ae16-b041-ff914ee94a93@linux.intel.com> (raw)
In-Reply-To: <20200214115634.30e8ebf2@gandalf.local.home>

On 14.2.2020 18.56, Steven Rostedt wrote:
> From: Steven Rostedt (VMware) <rostedt@goodmis.org>
> 
> libtraceevent (used by perf and trace-cmd) failed to parse the
> xhci_urb_dequeue trace event. This is because the user space trace
> event format parsing is not a full C compiler. It can handle some basic
> logic, but is not meant to be able to handle everything C can do.
> 
> In cases where a trace event field needs to be converted from a number
> to a string, there's the __print_symbolic() macro that should be used:
> 
>  See samples/trace_events/trace-events-sample.h
> 
> Some xhci trace events open coded the __print_symbolic() causing the
> user spaces tools to fail to parse it. This has to be replaced with
> __print_symbolic() instead.
> 
> CC: stable@vger.kernel.org
> Reported-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=206531
> Fixes: 5abdc2e6e12ff ("usb: host: xhci: add urb_enqueue/dequeue/giveback tracers")
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---

Thanks
Added to queue

-Mathias

      reply	other threads:[~2020-02-19  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 16:56 [PATCH] xhci: Do not open code __print_symbolic() in xhci trace events Steven Rostedt
2020-02-19  9:20 ` Mathias Nyman [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=c25679c6-de22-ae16-b041-ff914ee94a93@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=tstoyanov@vmware.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