From: Milian Wolff <milian.wolff@kdab.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Alexey Budankov <alexey.budankov@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dmitri Prokhorov <Dmitry.Prohorov@intel.com>
Subject: Re: [RFC PATCH] perf/core: exposing type of context-switch-out event
Date: Thu, 01 Mar 2018 21:57:07 +0100 [thread overview]
Message-ID: <8840260.4tRkpliXxk@agathebauer> (raw)
In-Reply-To: <20180301193659.GJ21543@tassilo.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Donnerstag, 1. März 2018 20:36:59 CET Andi Kleen wrote:
> > Please also add documentation Documentation/perf.data-file-format.txt, but
> > I just noticed that not even PERF_RECORD_SWITCH is documented there...
>
> That file only covers fields not generated by the kernel, but this
> is coming from the kernel.
>
> Kernel records are documented in the manpage, but Vince usually updates
> that on his own.
Ah, TIL - thanks for that tip! But I still think it would be good to have a
complete documentation of the perf.data file format in one place. I guess
patches would be welcome to add more aspects of the file format there, even if
it's generated by the kernel? That helps for thirdparty tools that parse the
perf.data files (like perfparser used by QtCreator and hotspot).
Cheers
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3826 bytes --]
prev parent reply other threads:[~2018-03-01 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 15:40 [RFC PATCH] perf/core: exposing type of context-switch-out event Alexey Budankov
2018-03-01 18:08 ` Andi Kleen
2018-03-01 19:19 ` Milian Wolff
2018-03-01 19:36 ` Andi Kleen
2018-03-01 20:57 ` Milian Wolff [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=8840260.4tRkpliXxk@agathebauer \
--to=milian.wolff@kdab.com \
--cc=Dmitry.Prohorov@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox