Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1605366
| From | Alexander Shishkin <alexander.shishkin@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] stm class: Document the stm_ftrace |
| Date | 2017-03-21 08:40 +0100 |
| Message-ID | <tnmyB-8M-9@gated-at.bofh.it> (permalink) |
| References | <tmZiH-RH-19@gated-at.bofh.it> <tn1DP-2AT-5@gated-at.bofh.it> <tn3cC-3xv-13@gated-at.bofh.it> <tn3vZ-3VF-33@gated-at.bofh.it> <tnl9v-7Kc-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 21 March 2017 at 07:57, Chunyan Zhang <zhang.lyra@gmail.com> wrote: > On 20 March 2017 at 19:09, Alexander Shishkin > <alexander.shishkin@linux.intel.com> wrote: >> 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 > > In fact I had implemented exporting tracepoints to STM and tried > upstreaming that, but Steven Rostedt and Ingo expressed their worries > on that would introduce a considerable impact on Ftrace fast path > since a tracepoint basically was a string which was too long to be > written to STM with some acceptable impact on fast path, so I stopped > upstreaming that feature. Did we ever consider writing a string pointer (or even on offset into the corresponding section, to avoid KASLR fun) instead of the actual string? This would require a kernel binary on the decoding end, though. Regards, -- Alex
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] stm class: Document the stm_ftrace Chunyan Zhang <chunyan.zhang@spreadtrum.com> - 2017-03-20 07:50 +0100
Re: [PATCH] stm class: Document the stm_ftrace Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2017-03-20 10:20 +0100
Re: [PATCH] stm class: Document the stm_ftrace Chunyan Zhang <zhang.lyra@gmail.com> - 2017-03-20 12:00 +0100
Re: [PATCH] stm class: Document the stm_ftrace Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2017-03-20 12:20 +0100
Re: [PATCH] stm class: Document the stm_ftrace Chunyan Zhang <zhang.lyra@gmail.com> - 2017-03-21 07:10 +0100
Re: [PATCH] stm class: Document the stm_ftrace Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2017-03-21 08:40 +0100
Re: [PATCH] stm class: Document the stm_ftrace Chunyan Zhang <zhang.lyra@gmail.com> - 2017-03-21 13:30 +0100
csiph-web