From: Leo Yan <leo.yan@linaro.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Kees Cook <keescook@chromium.org>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Nicholas Piggin <npiggin@gmail.com>,
James Morse <james.morse@arm.com>, Marc Zyngier <maz@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Peter Collingbourne <pcc@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
James Clark <james.clark@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFCv1 4/4] perf: arm_spe: Dynamically switch PID tracing to contextidr
Date: Fri, 17 Dec 2021 15:58:50 +0800 [thread overview]
Message-ID: <20211217075850.GC371207@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20211210075918.GD622826@leoy-ThinkPad-X240s>
On Fri, Dec 10, 2021 at 03:59:18PM +0800, Leo Yan wrote:
[...]
> > You could also check there if the PID is in the root
> > namespace and avoid setting CONTEXTIDR (or write 0).
>
> This could introduce mess. Writing 0 can lead the decoder to take it
> as idle thread; if skip setting CONTEXTIDR, the tracer might use a
> stale stale PID number (the previous one ID number).
>
> Alternatively, if you accept to always set PID to CONTEXTIDR in
> contextidr_thread_switch(), it would be fine for me and we can only
> need to control PID packets in SPE and CoreSight drivers.
>
> Please let me know your opinion, thanks!
Gentle ping, Catalin. If anything is blur and you want me to clarify,
please let me know. Sorry if you are in holiday and if so we can
delay after holiday.
Thanks,
Leo
_______________________________________________
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-12-17 8:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 13:45 [RFCv1 0/4] arm64: Use static key for PID in CONTEXTIDR Leo Yan
2021-10-21 13:45 ` [RFCv1 1/4] arm64: Use static key for tracing " Leo Yan
2021-10-21 14:33 ` James Clark
2021-10-21 14:37 ` Leo Yan
2021-10-21 15:47 ` Kees Cook
2021-10-21 13:45 ` [RFCv1 2/4] arm64: entry: Always apply workaround for contextidr_el1 Leo Yan
2021-10-21 13:45 ` [RFCv1 3/4] arm64: Introduce functions for controlling PID tracing Leo Yan
2021-10-21 13:45 ` [RFCv1 4/4] perf: arm_spe: Dynamically switch PID tracing to contextidr Leo Yan
2021-10-21 15:49 ` Kees Cook
2021-10-22 2:09 ` Leo Yan
2021-11-01 15:28 ` Leo Yan
2021-12-03 16:22 ` Catalin Marinas
2021-12-05 13:51 ` Leo Yan
2021-12-07 11:48 ` Catalin Marinas
2021-12-07 12:31 ` Leo Yan
2021-12-08 17:29 ` Catalin Marinas
2021-12-10 7:59 ` Leo Yan
2021-12-17 7:58 ` Leo Yan [this message]
2022-01-17 18:48 ` Catalin Marinas
2022-02-01 13:02 ` Leo Yan
2021-10-22 15:36 ` James Clark
2021-10-22 15:40 ` James Clark
2021-10-22 16:23 ` James Clark
2021-10-24 10:25 ` Leo Yan
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=20211217075850.GC371207@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=eranian@google.com \
--cc=james.clark@arm.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=npiggin@gmail.com \
--cc=pcc@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.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