From: Borislav Petkov <bp@alien8.de>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: linux-tip-commits@vger.kernel.org,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Brendan Gregg" <brendan.d.gregg@gmail.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Luis Cláudio Gonçalves" <lclaudio@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Ingo Molnar" <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [tip: perf/core] perf trace: Introduce --filter for tracepoint events
Date: Thu, 17 Oct 2019 09:12:05 +0200 [thread overview]
Message-ID: <20191017071205.GA14441@zn.tnic> (raw)
In-Reply-To: <157111750352.12254.17113253973879925388.tip-bot2@tip-bot2>
On Tue, Oct 15, 2019 at 05:31:43AM -0000, tip-bot2 for Arnaldo Carvalho de Melo wrote:
> The following commit has been merged into the perf/core branch of tip:
>
> Commit-ID: d4097f1937f2242d0aa0a7c654d2159a6895e5c8
> Gitweb: https://git.kernel.org/tip/d4097f1937f2242d0aa0a7c654d2159a6895e5c8
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> AuthorDate: Tue, 08 Oct 2019 07:33:08 -03:00
> Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
> CommitterDate: Wed, 09 Oct 2019 11:23:52 -03:00
>
> perf trace: Introduce --filter for tracepoint events
>
> Similar to what is in 'perf record', works just like there:
>
> # perf trace -e msr:*
> 328.297 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.302 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.306 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.317 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.322 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.327 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.331 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.336 :0/0 msr:write_msr(msr: FS_BASE, val: 140240388381888)
> 328.340 :0/0 ^Cmsr:write_msr(msr: FS_BASE, val: 140240388381888)
I wonder if you guys can force this val:'s format to be always hex?
Because MSR values are a lot more "natural" in hex...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-10-17 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-95bfe5d4tzy5f66bx49d05rj@git.kernel.org>
2019-10-15 5:31 ` [tip: perf/core] perf trace: Introduce --filter for tracepoint events tip-bot2 for Arnaldo Carvalho de Melo
2019-10-17 7:12 ` Borislav Petkov [this message]
2019-10-17 13:13 ` Arnaldo Carvalho de Melo
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=20191017071205.GA14441@zn.tnic \
--to=bp@alien8.de \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=brendan.d.gregg@gmail.com \
--cc=jolsa@kernel.org \
--cc=lclaudio@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mtosatti@redhat.com \
--cc=namhyung@kernel.org \
/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.