From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
coresight@lists.linaro.org
Subject: Re: [PATCH v2] coresight: trbe: Move check for kernel page table isolation from EL0 to probe
Date: Fri, 4 Feb 2022 08:20:23 +0530 [thread overview]
Message-ID: <ede31a2c-2d5b-88bd-9687-848eee2a0040@arm.com> (raw)
In-Reply-To: <20220203190159.3145272-1-sudeep.holla@arm.com>
On 2/4/22 12:31 AM, Sudeep Holla wrote:
> Currently with the check present in the module initialisation, it shouts
> on all the systems irrespective of presence of coresight trace buffer
> extensions.
>
> Similar to Arm SPE perf driver, move the check for kernel page table
> isolation from EL0 to the device probe stage instead of the module
> initialisation so that it complains only on the systems that support TRBE.
>
> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: Mike Leach <mike.leach@linaro.org>
> Cc: Leo Yan <leo.yan@linaro.org>
> Cc: Anshuman Khandual <anshuman.khandual@arm.com>
> Cc: coresight@lists.linaro.org
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> drivers/hwtracing/coresight/coresight-trbe.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> v1[1]->v2:
> - Added comment about trace capture being not possible with kernel
> page table isolation
> [1] https://lore.kernel.org/r/20220201122212.3009461-1-sudeep.holla@arm.com
>
> diff --git a/drivers/hwtracing/coresight/coresight-trbe.c b/drivers/hwtracing/coresight/coresight-trbe.c
> index 276862c07e32..3e37a63cb7d2 100644
> --- a/drivers/hwtracing/coresight/coresight-trbe.c
> +++ b/drivers/hwtracing/coresight/coresight-trbe.c
> @@ -1423,6 +1423,12 @@ static int arm_trbe_device_probe(struct platform_device *pdev)
> struct device *dev = &pdev->dev;
> int ret;
>
> + /* Trace capture is not possible with kernel page table isolation */
> + if (arm64_kernel_unmapped_at_el0()) {
> + pr_err("TRBE wouldn't work if kernel gets unmapped at EL0\n");
> + return -EOPNOTSUPP;
> + }
> +
> drvdata = devm_kzalloc(dev, sizeof(*drvdata), GFP_KERNEL);
> if (!drvdata)
> return -ENOMEM;
> @@ -1484,11 +1490,6 @@ static int __init arm_trbe_init(void)
> {
> int ret;
>
> - if (arm64_kernel_unmapped_at_el0()) {
> - pr_err("TRBE wouldn't work if kernel gets unmapped at EL0\n");
> - return -EOPNOTSUPP;
> - }
> -
> ret = platform_driver_register(&arm_trbe_driver);
> if (!ret)
> return 0;
>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
next prev parent reply other threads:[~2022-02-04 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 19:01 Sudeep Holla
2022-02-04 2:50 ` Anshuman Khandual [this message]
2022-02-04 12:02 ` Suzuki K Poulose
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=ede31a2c-2d5b-88bd-9687-848eee2a0040@arm.com \
--to=anshuman.khandual@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=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
/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®