From: James Clark <james.clark@arm.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Mark Brown <broonie@kernel.org>
Cc: coresight@lists.linaro.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com,
mike.leach@linaro.org, leo.yan@linaro.org,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 1/1] arm64: defconfig: Add Coresight as module
Date: Thu, 22 Sep 2022 10:04:09 +0100 [thread overview]
Message-ID: <07d37df2-246e-70ea-4a9f-e33354d8864d@arm.com> (raw)
In-Reply-To: <20220921164622.GA1124503@p14s>
On 21/09/2022 17:46, Mathieu Poirier wrote:
> On Wed, Sep 21, 2022 at 04:26:59PM +0100, Mark Brown wrote:
>> On Wed, Sep 21, 2022 at 03:05:35PM +0100, James Clark wrote:
>>
>>> +CONFIG_CORESIGHT_CTI=m
>>> +CONFIG_CORESIGHT_CTI_INTEGRATION_REGS=y
>>
>
> I agree - integration registers should not be enabled by default.
>
>> Do we want this turned on by default? According to the
>> description it's a bit dangerous and it's exposed via sysfs
>> rather than debugfs.
>
>
Should I disable just CONFIG_CORESIGHT_CTI_INTEGRATION_REGS or
CONFIG_CORESIGHT_CTI as well? There are other writable registers exposed
via sysfs outside of these two options, so I wanted to check if it's
just the integration registers that are the issue.
_______________________________________________
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:[~2022-09-22 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:05 [PATCH 0/1] arm64: defconfig: Add Coresight as module James Clark
2022-09-21 14:05 ` [PATCH 1/1] " James Clark
2022-09-21 15:26 ` Mark Brown
2022-09-21 16:46 ` Mathieu Poirier
2022-09-22 9:04 ` James Clark [this message]
2022-09-22 9:26 ` Suzuki K Poulose
2022-09-21 15:08 ` [PATCH 0/1] " Catalin Marinas
2022-09-22 9:34 ` James Clark
2022-09-22 10:52 ` Catalin Marinas
2022-09-22 13:06 ` James Clark
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=07d37df2-246e-70ea-4a9f-e33354d8864d@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;
as well as URLs for NNTP newsgroup(s).