From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Mike Leach <mike.leach@linaro.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Coresight ML <coresight@lists.linaro.org>,
Stephen Boyd <swboyd@chromium.org>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 2/2] coresight: tmc: Add shutdown callback for TMC ETR/ETF
Date: Mon, 08 Jun 2020 19:37:43 +0530 [thread overview]
Message-ID: <dfa6aa626f075f49d9ba1ae8ffa3d384@codeaurora.org> (raw)
In-Reply-To: <da1fdf765ea29cfe7a44145b17431721@codeaurora.org>
Hi Mathieu, Mike
On 2020-06-04 12:57, Sai Prakash Ranjan wrote:
>
[...]
>>
>> Robin has a point - user space is long gone at this time. As such the
>> first
>> question to ask is what kind of CS session was running at the time the
>> system
>> was shutting down. Was it a perf session of a sysfs session?
>>
>> I'm guessing it was a sysfs session because user space has been blown
>> away a
>> while back and part of that process should have killed all perf
>> sessions.
>
> I was enabling trace via sysfs.
>
>>
>> If I am correct then simply switching off the ETR HW in the shutdown()
>> amba bus
>> callback should be fine - otherwise Mike's approach is mandatory.
>> There is
>> also the exchange between Robin and Sai about removing the SMMU
>> shutdown
>> callback, but that thread is still incomplete.
>>
>
> If Robin is hinting at removing SMMU shutdown callback, then I think
> adding
> all these shutdown callbacks to all clients of SMMU can be avoided. Git
> blaming
> the thing shows it was added to avoid some kexec memory corruption.
>
I think I misread the cryptic hint from Robin and it is not right to
remove
SMMU shutdown callback. For more details on why that was a bad idea and
would
break kexec, please refer to [1].
As for the coresight, can I disable the ETR only in the tmc shutdown
callback
or are we still concerned about the userspace coming into picture?
[1] https://lore.kernel.org/patchwork/patch/1253131/
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Mike Leach <mike.leach@linaro.org>
Cc: Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-msm@vger.kernel.org,
Coresight ML <coresight@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] coresight: tmc: Add shutdown callback for TMC ETR/ETF
Date: Mon, 08 Jun 2020 19:37:43 +0530 [thread overview]
Message-ID: <dfa6aa626f075f49d9ba1ae8ffa3d384@codeaurora.org> (raw)
In-Reply-To: <da1fdf765ea29cfe7a44145b17431721@codeaurora.org>
Hi Mathieu, Mike
On 2020-06-04 12:57, Sai Prakash Ranjan wrote:
>
[...]
>>
>> Robin has a point - user space is long gone at this time. As such the
>> first
>> question to ask is what kind of CS session was running at the time the
>> system
>> was shutting down. Was it a perf session of a sysfs session?
>>
>> I'm guessing it was a sysfs session because user space has been blown
>> away a
>> while back and part of that process should have killed all perf
>> sessions.
>
> I was enabling trace via sysfs.
>
>>
>> If I am correct then simply switching off the ETR HW in the shutdown()
>> amba bus
>> callback should be fine - otherwise Mike's approach is mandatory.
>> There is
>> also the exchange between Robin and Sai about removing the SMMU
>> shutdown
>> callback, but that thread is still incomplete.
>>
>
> If Robin is hinting at removing SMMU shutdown callback, then I think
> adding
> all these shutdown callbacks to all clients of SMMU can be avoided. Git
> blaming
> the thing shows it was added to avoid some kexec memory corruption.
>
I think I misread the cryptic hint from Robin and it is not right to
remove
SMMU shutdown callback. For more details on why that was a bad idea and
would
break kexec, please refer to [1].
As for the coresight, can I disable the ETR only in the tmc shutdown
callback
or are we still concerned about the userspace coming into picture?
[1] https://lore.kernel.org/patchwork/patch/1253131/
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
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:[~2020-06-08 14:07 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 8:02 [PATCH 0/2] coresight: tmc: Add shutdown callback for TMC ETR/ETF Sai Prakash Ranjan
2020-06-01 8:02 ` Sai Prakash Ranjan
2020-06-01 8:02 ` [PATCH 1/2] coresight: tmc: Add enable flag to indicate the status of ETR/ETF Sai Prakash Ranjan
2020-06-01 8:02 ` Sai Prakash Ranjan
2020-06-01 13:27 ` Mike Leach
2020-06-01 13:27 ` Mike Leach
2020-06-01 17:13 ` Sai Prakash Ranjan
2020-06-01 17:13 ` Sai Prakash Ranjan
2020-06-01 8:02 ` [PATCH 2/2] coresight: tmc: Add shutdown callback for TMC ETR/ETF Sai Prakash Ranjan
2020-06-01 8:02 ` Sai Prakash Ranjan
2020-06-01 13:35 ` Mike Leach
2020-06-01 13:35 ` Mike Leach
2020-06-01 17:15 ` Sai Prakash Ranjan
2020-06-01 17:15 ` Sai Prakash Ranjan
2020-06-01 21:28 ` Mathieu Poirier
2020-06-01 21:28 ` Mathieu Poirier
2020-06-02 7:30 ` Sai Prakash Ranjan
2020-06-02 7:30 ` Sai Prakash Ranjan
2020-06-02 22:12 ` Mike Leach
2020-06-02 22:12 ` Mike Leach
2020-06-03 10:24 ` Sai Prakash Ranjan
2020-06-03 10:24 ` Sai Prakash Ranjan
2020-06-03 11:27 ` Mike Leach
2020-06-03 11:27 ` Mike Leach
2020-06-03 12:14 ` Sai Prakash Ranjan
2020-06-03 12:14 ` Sai Prakash Ranjan
2020-06-03 13:22 ` Mike Leach
2020-06-03 13:22 ` Mike Leach
2020-06-03 13:34 ` Robin Murphy
2020-06-03 13:34 ` Robin Murphy
2020-06-03 13:43 ` Sai Prakash Ranjan
2020-06-03 13:43 ` Sai Prakash Ranjan
2020-06-03 13:51 ` Mike Leach
2020-06-03 13:51 ` Mike Leach
2020-06-03 14:02 ` Sai Prakash Ranjan
2020-06-03 14:02 ` Sai Prakash Ranjan
2020-06-03 17:44 ` Mathieu Poirier
2020-06-03 17:44 ` Mathieu Poirier
2020-06-04 7:27 ` Sai Prakash Ranjan
2020-06-04 7:27 ` Sai Prakash Ranjan
2020-06-08 14:07 ` Sai Prakash Ranjan [this message]
2020-06-08 14:07 ` Sai Prakash Ranjan
2020-06-09 15:27 ` Mathieu Poirier
2020-06-09 15:27 ` Mathieu Poirier
2020-06-09 15:37 ` Sai Prakash Ranjan
2020-06-09 15:37 ` Sai Prakash Ranjan
2020-06-03 11:37 ` Robin Murphy
2020-06-03 11:37 ` Robin Murphy
2020-06-03 12:00 ` Sai Prakash Ranjan
2020-06-03 12:00 ` Sai Prakash Ranjan
2020-06-03 12:21 ` Robin Murphy
2020-06-03 12:21 ` Robin Murphy
2020-06-03 12:26 ` Sai Prakash Ranjan
2020-06-03 12:26 ` Sai Prakash Ranjan
2020-06-03 13:40 ` Robin Murphy
2020-06-03 13:40 ` Robin Murphy
2020-06-03 13:51 ` Sai Prakash Ranjan
2020-06-03 13:51 ` Sai Prakash Ranjan
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=dfa6aa626f075f49d9ba1ae8ffa3d384@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=swboyd@chromium.org \
--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 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.