From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Chunyan Zhang <chunyan.zhang@spreadtrum.com>,
"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
nicolas.guion@st.com
Subject: Re: [PATCH] stm class: Document the stm_ftrace
Date: Mon, 20 Mar 2017 13:09:54 +0200 [thread overview]
Message-ID: <87wpbk2ohp.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CAAfSe-uZK0X41rMrSsHPCgssjN9dty43VxsyVtX1Hd01FgJ77w@mail.gmail.com>
Chunyan Zhang <zhang.lyra@gmail.com> writes:
> Hi Alex,
>
> On 20 March 2017 at 16:49, Alexander Shishkin
> <alexander.shishkin@linux.intel.com> wrote:
>> Hi Chunyan,
>>
>> A couple of clarifications: iirc this applies to the function tracer
>> of ftrace, right? Does it make sense to mention that? Also, are you
>
> Right, only applies to the function tracer currently (actually only
> function address and parent function address of Function tracer is
> recorded into STM, I mean it doesn't include like "pid" "task name"
> "cpu-id" these information right now). It makes sense to mention
> function tracer, I will address that.
Thanks!
>> planning to support other ftrace payloads like trace_printk()s?
>
> No plan so far, but I think I can consider to do that, it depends on
> how many people think that are helpful.
> What do you think?
Well, I myself almost never use function tracer, but I do use
tracepoints/trace_printk()s. I'm *guessing* that everybody who's
subsystem implement tracepoints will be interested in those.
I confess that I haven't yet looked at the code properly, so I'm a don't
have a picture of what it will take to implement these.
Regards,
--
Alex
next prev parent reply other threads:[~2017-03-20 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 6:47 Chunyan Zhang
2017-03-20 8:49 ` Alexander Shishkin
2017-03-20 10:58 ` Chunyan Zhang
2017-03-20 11:09 ` Alexander Shishkin [this message]
2017-03-21 5:57 ` Chunyan Zhang
2017-03-21 7:33 ` Alexander Shishkin
2017-03-21 12:26 ` Chunyan Zhang
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=87wpbk2ohp.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=chunyan.zhang@spreadtrum.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nicolas.guion@st.com \
--cc=zhang.lyra@gmail.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
Powered by JetHome