From: Steven Rostedt <rostedt@goodmis.org>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
linux-kernel@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] tee: optee: add invoke_fn tracepoints
Date: Wed, 10 Feb 2021 09:37:36 -0500 [thread overview]
Message-ID: <20210210093736.0b26f917@gandalf.local.home> (raw)
In-Reply-To: <20210210144409.36ecdaed@xhacker.debian>
On Wed, 10 Feb 2021 14:44:09 +0800
Jisheng Zhang <Jisheng.Zhang@synaptics.com> wrote:
> Add tracepoints to retrieve information about the invoke_fn. This would
> help to measure how many invoke_fn are triggered and how long it takes
> to complete one invoke_fn call.
>
> Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> ---
>
> Since v1:
> - add BUILD_BUG_ON() macro usage to make sure that the size of what is being
> copied, is not smaller than the amount being copied. Thank Steve.
> - move optee_trace.h to keep include headers sorted
From a tracing point of view:
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: op-tee@lists.trustedfirmware.org,
Jens Wiklander <jens.wiklander@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tee: optee: add invoke_fn tracepoints
Date: Wed, 10 Feb 2021 09:37:36 -0500 [thread overview]
Message-ID: <20210210093736.0b26f917@gandalf.local.home> (raw)
In-Reply-To: <20210210144409.36ecdaed@xhacker.debian>
On Wed, 10 Feb 2021 14:44:09 +0800
Jisheng Zhang <Jisheng.Zhang@synaptics.com> wrote:
> Add tracepoints to retrieve information about the invoke_fn. This would
> help to measure how many invoke_fn are triggered and how long it takes
> to complete one invoke_fn call.
>
> Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> ---
>
> Since v1:
> - add BUILD_BUG_ON() macro usage to make sure that the size of what is being
> copied, is not smaller than the amount being copied. Thank Steve.
> - move optee_trace.h to keep include headers sorted
From a tracing point of view:
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 14:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 6:44 [PATCH] tee: optee: add invoke_fn tracepoints Jisheng Zhang
2021-02-10 6:44 ` Jisheng Zhang
2021-02-10 14:37 ` Steven Rostedt [this message]
2021-02-10 14:37 ` Steven Rostedt
2021-02-23 7:59 ` Jens Wiklander
2021-02-23 7:59 ` Jens Wiklander
2021-02-23 10:40 ` Jisheng Zhang
2021-02-23 10:40 ` Jisheng Zhang
2021-02-23 13:11 ` Jens Wiklander
2021-02-23 13:11 ` Jens Wiklander
2021-02-23 14:19 ` Steven Rostedt
2021-02-23 14:19 ` Steven Rostedt
2021-02-24 8:10 ` Jens Wiklander
2021-02-24 8:10 ` Jens Wiklander
2021-03-24 14:34 ` Guenter Roeck
2021-03-24 14:34 ` Guenter Roeck
2021-03-24 14:48 ` Guenter Roeck
2021-03-24 14:48 ` Guenter Roeck
2021-03-24 14:53 ` Steven Rostedt
2021-03-24 14:53 ` Steven Rostedt
2021-03-25 3:50 ` Jisheng Zhang
2021-03-25 3:50 ` Jisheng Zhang
2021-03-25 7:49 ` Jens Wiklander
2021-03-25 7:49 ` Jens Wiklander
-- strict thread matches above, loose matches on Subject: below --
2021-02-09 11:02 Jisheng Zhang
2021-02-09 11:02 ` Jisheng Zhang
2021-02-09 15:58 ` Steven Rostedt
2021-02-09 15:58 ` Steven Rostedt
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=20210210093736.0b26f917@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.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.