From: Andrew Murray <andrew.murray@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: alexander.shishkin@linux.intel.com,
linux-arm-kernel@lists.infradead.org, mathieu.poirier@linaro.org
Subject: Re: [PATCH v1 0/5] coresight: etm4x: save/restore ETMv4 context across CPU low power states
Date: Thu, 20 Jun 2019 17:57:14 +0100 [thread overview]
Message-ID: <20190620165714.GI20984@e119886-lin.cambridge.arm.com> (raw)
In-Reply-To: <1e4193ca-ebd2-920a-dc88-127ffc279990@arm.com>
On Thu, Jun 20, 2019 at 05:45:11PM +0100, Suzuki K Poulose wrote:
>
>
> On 18/06/2019 13:54, Andrew Murray wrote:
> > Some hardware will ignore bit TRCPDCR.PU which is used to signal
> > to hardware that power should not be removed from the trace unit.
> > Let's mitigate against this by saving and restoring the trace
> > unit state when the CPU enters low power states.
> >
> > To provide a benefit to both self-hosted and external debuggers
> > we save/restore the entire state which includes etmv4_config data
> > and dynamic data such as inflight counter values, sequencer
> > states, etc.
>
> Andrew,
>
> Please could you also mention that there is a kernel command line parameter
> to control the save/restore here and in the patch which introduces it ?
> I think this missing information is creating the confusion.
Yes sure.
Thanks,
Andrew Murray
>
> Cheers
> Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-20 16:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 12:54 [PATCH v1 0/5] coresight: etm4x: save/restore ETMv4 context across CPU low power states Andrew Murray
2019-06-18 12:54 ` [PATCH v1 1/5] coresight: etm4x: remove superfluous setting of os_unlock Andrew Murray
2019-06-19 10:42 ` Suzuki K Poulose
2019-06-18 12:54 ` [PATCH v1 2/5] coresight: etm4x: use explicit barriers on enable/disable Andrew Murray
2019-06-18 22:34 ` Mathieu Poirier
2019-06-19 8:32 ` Suzuki K Poulose
2019-06-20 10:25 ` Andrew Murray
2019-06-18 12:54 ` [PATCH v1 3/5] coresight: etm4x: use octal permissions for module_params Andrew Murray
2019-06-19 10:43 ` Suzuki K Poulose
2019-06-18 12:54 ` [PATCH v1 4/5] coresight: etm4x: improve clarity of etm4_os_unlock comment Andrew Murray
2019-06-19 10:46 ` Suzuki K Poulose
2019-06-20 10:29 ` Andrew Murray
2019-06-18 12:54 ` [PATCH v1 5/5] coresight: etm4x: save/restore state across CPU low power states Andrew Murray
2019-06-18 13:21 ` Sudeep Holla
2019-06-19 10:38 ` Suzuki K Poulose
2019-06-19 11:07 ` Sudeep Holla
2019-06-19 16:22 ` Mathieu Poirier
2019-06-20 11:41 ` Andrew Murray
2019-06-20 14:55 ` Mathieu Poirier
2019-06-20 15:41 ` Sudeep Holla
2019-06-20 16:14 ` Mathieu Poirier
2019-06-20 16:34 ` Sudeep Holla
2019-06-20 16:47 ` Mathieu Poirier
2019-06-20 16:52 ` Sudeep Holla
2019-06-20 16:54 ` Andrew Murray
2019-06-20 17:00 ` Suzuki K Poulose
2019-06-20 17:10 ` Mathieu Poirier
2019-06-21 9:29 ` Andrew Murray
2019-06-21 15:30 ` Mathieu Poirier
2019-06-20 17:11 ` Sudeep Holla
2019-06-20 18:00 ` Mathieu Poirier
2019-06-20 16:48 ` Sudeep Holla
2019-06-18 22:55 ` Mathieu Poirier
2019-06-20 11:07 ` Andrew Murray
2019-06-20 14:49 ` Mathieu Poirier
2019-06-20 15:11 ` Andrew Murray
2019-06-20 15:26 ` Mathieu Poirier
2019-06-25 10:07 ` Suzuki K Poulose
2019-06-25 19:57 ` Mathieu Poirier
2019-06-26 10:21 ` Mike Leach
2019-06-26 16:57 ` Mathieu Poirier
2019-06-27 8:12 ` Andrew Murray
2019-06-27 8:17 ` Andrew Murray
2019-06-20 16:45 ` [PATCH v1 0/5] coresight: etm4x: save/restore ETMv4 context " Suzuki K Poulose
2019-06-20 16:57 ` Andrew Murray [this message]
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=20190620165714.GI20984@e119886-lin.cambridge.arm.com \
--to=andrew.murray@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).