From: James Clark <james.clark@arm.com>
To: coresight@lists.linaro.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org
Cc: suzuki.poulose@arm.com, mathieu.poirier@linaro.org,
mike.leach@linaro.org, leo.yan@linaro.org, broonie@kernel.org,
linux-kernel@vger.kernel.org, James Clark <james.clark@arm.com>,
Will Deacon <will@kernel.org>
Subject: [PATCH v2 0/1] arm64: defconfig: Add Coresight as module
Date: Thu, 22 Sep 2022 15:23:59 +0100 [thread overview]
Message-ID: <20220922142400.478815-1-james.clark@arm.com> (raw)
I'm still leaving out CONFIG_CORESIGHT_SOURCE_ETM4X because it depends
on the outcome of the investigation into CONFIG_PID_IN_CONTEXTIDR, but
I think we should enable these ones for now and start getting some of
the benefits sooner.
Changes since v1:
* Remove CONFIG_CORESIGHT_CTI_INTEGRATION_REGS=y which shouldn't be
enabled by default
-----
As suggested by Catalin here's the change to add Coresight to defconfig.
Unfortunately I don't think we should add CONFIG_CORESIGHT_SOURCE_ETM4X
which builds a few files until [1] is merged because of the overhead
of CONFIG_PID_IN_CONTEXTIDR.
[1]: https://lore.kernel.org/lkml/20211021134530.206216-1-leo.yan@linaro.org/T/
applies to arm64/for-next/core (e99db032d186)
James Clark (1):
arm64: defconfig: Add Coresight as module
arch/arm64/configs/defconfig | 8 ++++++++
1 file changed, 8 insertions(+)
--
2.28.0
next reply other threads:[~2022-09-22 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:23 James Clark [this message]
2022-09-22 14:24 ` [PATCH v2 1/1] " James Clark
2022-09-29 17:53 ` [PATCH v2 0/1] " Catalin Marinas
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=20220922142400.478815-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@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
all inboxes | Powered by JetHome®