linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zhang.chunyan@linaro.org (Chunyan Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V8 3/3] stm: Mark the functions of writing buffer with notrace
Date: Mon, 21 Nov 2016 10:24:44 +0800	[thread overview]
Message-ID: <CAG2=9p_X4GD7w4FdTK3M_3OZ1-KDSP__qOKoM5FGaxk07ERqbA@mail.gmail.com> (raw)
In-Reply-To: <871sy8g83q.fsf@ashishki-desk.ger.corp.intel.com>

On 18 November 2016 at 22:45, Alexander Shishkin
<alexander.shishkin@linux.intel.com> wrote:
> Chunyan Zhang <zhang.chunyan@linaro.org> writes:
>
>> If CONFIG_STM_SOURCE_FTRACE is selected, Function trace data can be writen
>> to sink via STM, all functions that related to writing data packets to
>> STM should be marked 'notrace' to avoid being traced by Ftrace, otherwise
>> the program would stall into an endless loop.
>>
>> Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
>> Acked-by: Steven Rostedt <rostedt@goodmis.org>
>> ---
>>  drivers/hwtracing/coresight/coresight-stm.c |  2 +-
>>  drivers/hwtracing/intel_th/sth.c            | 11 +++++++----
>>  drivers/hwtracing/stm/core.c                |  7 ++++---
>>  drivers/hwtracing/stm/dummy_stm.c           |  2 +-
>>  include/linux/stm.h                         |  4 ++--
>>  5 files changed, 15 insertions(+), 11 deletions(-)
>
> Quick nit: can you please split this one in 4: one for Coresight, one
> for Intel TH, one for stm/dummy and one for stm/core?

Sure, will do.

>
> I'd like to keep the bisectability. Otherwise, this is fine by me:
>
> Acked-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>

Thanks,
Chunyan

>
> Regards,
> --
> Alex

      reply	other threads:[~2016-11-21  2:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18  3:07 [PATCH V8 0/3] Integration of function trace with System Trace IP blocks Chunyan Zhang
2016-11-18  3:07 ` [PATCH V8 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only Chunyan Zhang
2016-11-18 14:29   ` Steven Rostedt
2016-11-18 14:57     ` Alexander Shishkin
2016-11-18 16:45       ` Steven Rostedt
2016-11-21  3:18         ` Chunyan Zhang
2016-11-18  3:07 ` [PATCH V8 2/3] stm class: ftrace: Add ftrace-export-over-stm driver Chunyan Zhang
2016-11-18 14:45   ` Alexander Shishkin
2016-11-18  3:07 ` [PATCH V8 3/3] stm: Mark the functions of writing buffer with notrace Chunyan Zhang
2016-11-18 14:45   ` Alexander Shishkin
2016-11-21  2:24     ` Chunyan Zhang [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='CAG2=9p_X4GD7w4FdTK3M_3OZ1-KDSP__qOKoM5FGaxk07ERqbA@mail.gmail.com' \
    --to=zhang.chunyan@linaro.org \
    --cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).