From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH] tee: optee: add invoke_fn tracepoints
Date: Thu, 25 Mar 2021 11:50:43 +0800 [thread overview]
Message-ID: <20210325115043.6c00a33e@xhacker.debian> (raw)
In-Reply-To: <20210324105313.4ff3ad07@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]
On Wed, 24 Mar 2021 10:53:13 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 24 Mar 2021 07:48:53 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On Wed, Mar 24, 2021 at 07:34:07AM -0700, Guenter Roeck wrote:
> > > On Wed, Feb 10, 2021 at 02:44:09PM +0800, Jisheng Zhang 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>
> > >
> > > arm64:defconfig:
> > >
> > > make-arm64 -j drivers/tee/optee/call.o
> > > CALL scripts/atomic/check-atomics.sh
> > > CALL scripts/checksyscalls.sh
> > > CC drivers/tee/optee/call.o
> > > In file included from drivers/tee/optee/optee_trace.h:67,
> > > from drivers/tee/optee/call.c:18:
> > > ./include/trace/define_trace.h:95:42: fatal error: ./optee_trace.h: No such file or directory
> > > 95 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
> > > | ^
> > > compilation terminated.
Interesting, I always build linux kernel with "O=", didn't see such build error
and IIRC, we didn't receive any lkp robot build error report.
My steps are:
mkdir /tmp/test
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=/tmp/test defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=/tmp/test drivers/tee/optee/
Today, I tried to build the linux kernel w/o "O=...", I reproduced this error!
This is the first time I saw "O=" make a different behavior.
I'll send out a patch to fix it.
Thanks
> > >
> >
> > The problem also affects arm:imx_v6_v7_defconfig.
> >
>
> I think it affects everything. The problem is that the
> drivers/tee/optee/Makefile needs to be updated with:
>
> CFLAGS_call.o := -I$(src)
>
> otherwise the compiler wont know how to find the path to optee_tree.h.
>
> This is described in:
>
> samples/trace_events/Makefile
Thank Steven for pointing this out.
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
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: Thu, 25 Mar 2021 11:50:43 +0800 [thread overview]
Message-ID: <20210325115043.6c00a33e@xhacker.debian> (raw)
In-Reply-To: <20210324105313.4ff3ad07@gandalf.local.home>
On Wed, 24 Mar 2021 10:53:13 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 24 Mar 2021 07:48:53 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On Wed, Mar 24, 2021 at 07:34:07AM -0700, Guenter Roeck wrote:
> > > On Wed, Feb 10, 2021 at 02:44:09PM +0800, Jisheng Zhang 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>
> > >
> > > arm64:defconfig:
> > >
> > > make-arm64 -j drivers/tee/optee/call.o
> > > CALL scripts/atomic/check-atomics.sh
> > > CALL scripts/checksyscalls.sh
> > > CC drivers/tee/optee/call.o
> > > In file included from drivers/tee/optee/optee_trace.h:67,
> > > from drivers/tee/optee/call.c:18:
> > > ./include/trace/define_trace.h:95:42: fatal error: ./optee_trace.h: No such file or directory
> > > 95 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
> > > | ^
> > > compilation terminated.
Interesting, I always build linux kernel with "O=", didn't see such build error
and IIRC, we didn't receive any lkp robot build error report.
My steps are:
mkdir /tmp/test
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=/tmp/test defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=/tmp/test drivers/tee/optee/
Today, I tried to build the linux kernel w/o "O=...", I reproduced this error!
This is the first time I saw "O=" make a different behavior.
I'll send out a patch to fix it.
Thanks
> > >
> >
> > The problem also affects arm:imx_v6_v7_defconfig.
> >
>
> I think it affects everything. The problem is that the
> drivers/tee/optee/Makefile needs to be updated with:
>
> CFLAGS_call.o := -I$(src)
>
> otherwise the compiler wont know how to find the path to optee_tree.h.
>
> This is described in:
>
> samples/trace_events/Makefile
Thank Steven for pointing this out.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
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: Thu, 25 Mar 2021 11:50:43 +0800 [thread overview]
Message-ID: <20210325115043.6c00a33e@xhacker.debian> (raw)
In-Reply-To: <20210324105313.4ff3ad07@gandalf.local.home>
On Wed, 24 Mar 2021 10:53:13 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 24 Mar 2021 07:48:53 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On Wed, Mar 24, 2021 at 07:34:07AM -0700, Guenter Roeck wrote:
> > > On Wed, Feb 10, 2021 at 02:44:09PM +0800, Jisheng Zhang 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>
> > >
> > > arm64:defconfig:
> > >
> > > make-arm64 -j drivers/tee/optee/call.o
> > > CALL scripts/atomic/check-atomics.sh
> > > CALL scripts/checksyscalls.sh
> > > CC drivers/tee/optee/call.o
> > > In file included from drivers/tee/optee/optee_trace.h:67,
> > > from drivers/tee/optee/call.c:18:
> > > ./include/trace/define_trace.h:95:42: fatal error: ./optee_trace.h: No such file or directory
> > > 95 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
> > > | ^
> > > compilation terminated.
Interesting, I always build linux kernel with "O=", didn't see such build error
and IIRC, we didn't receive any lkp robot build error report.
My steps are:
mkdir /tmp/test
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=/tmp/test defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=/tmp/test drivers/tee/optee/
Today, I tried to build the linux kernel w/o "O=...", I reproduced this error!
This is the first time I saw "O=" make a different behavior.
I'll send out a patch to fix it.
Thanks
> > >
> >
> > The problem also affects arm:imx_v6_v7_defconfig.
> >
>
> I think it affects everything. The problem is that the
> drivers/tee/optee/Makefile needs to be updated with:
>
> CFLAGS_call.o := -I$(src)
>
> otherwise the compiler wont know how to find the path to optee_tree.h.
>
> This is described in:
>
> samples/trace_events/Makefile
Thank Steven for pointing this out.
next prev parent reply other threads:[~2021-03-25 3:50 UTC|newest]
Thread overview: 42+ 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 6:44 ` Jisheng Zhang
2021-02-10 14:37 ` Steven Rostedt
2021-02-10 14:37 ` Steven Rostedt
2021-02-10 14:37 ` Steven Rostedt
2021-02-23 7:59 ` Jens Wiklander
2021-02-23 7:59 ` Jens Wiklander
2021-02-23 7:59 ` Jens Wiklander
2021-03-24 14:34 ` Guenter Roeck
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:48 ` Guenter Roeck
2021-03-24 14:53 ` Steven Rostedt
2021-03-24 14:53 ` Steven Rostedt
2021-03-24 14:53 ` Steven Rostedt
2021-03-25 3:50 ` Jisheng Zhang [this message]
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
2021-03-25 7:49 ` Jens Wiklander
[not found] < <CAHUa44E-_czjhRxr2JjggYu0sDCsRvOA3Uc=hqp7j5Cmtb9q0w@mail.gmail.com>
2021-02-23 10:40 ` Jisheng Zhang
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 13:11 ` Jens Wiklander
2021-02-23 14:19 ` Steven Rostedt
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-02-24 8:10 ` 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 11:02 ` Jisheng Zhang
2021-02-09 15:58 ` Steven Rostedt
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=20210325115043.6c00a33e@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--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.