On 02/05/18 14:52, Robin Murphy wrote:
On 02/05/18 04:55, Kim Phillips wrote:
On Tue, 1 May 2018 10:10:51 +0100
Suzuki K Poulose wrote:
Convert component enable/disable messages from dev_info to dev_dbg.
This is required to prevent LOCKDEP splats when operating in perf
mode where we could be
On Tue, May 01, 2018 at 10:10:51AM +0100, Suzuki K Poulose wrote:
> Convert component enable/disable messages from dev_info to dev_dbg.
> This is required to prevent LOCKDEP splats when operating in perf
> mode where we could be called with locks held to enable a coresight
> path. If someone wants
On 02/05/18 04:55, Kim Phillips wrote:
On Tue, 1 May 2018 10:10:51 +0100
Suzuki K Poulose wrote:
Convert component enable/disable messages from dev_info to dev_dbg.
This is required to prevent LOCKDEP splats when operating in perf
mode where we could be called with locks held to enable a cores
On 02/05/18 04:55, Kim Phillips wrote:
On Tue, 1 May 2018 10:10:51 +0100
Suzuki K Poulose wrote:
Convert component enable/disable messages from dev_info to dev_dbg.
This is required to prevent LOCKDEP splats when operating in perf
mode where we could be called with locks held to enable a cores
On Tue, 1 May 2018 10:10:51 +0100
Suzuki K Poulose wrote:
> Convert component enable/disable messages from dev_info to dev_dbg.
> This is required to prevent LOCKDEP splats when operating in perf
> mode where we could be called with locks held to enable a coresight
Can we see the splats? Doesn'
Convert component enable/disable messages from dev_info to dev_dbg.
This is required to prevent LOCKDEP splats when operating in perf
mode where we could be called with locks held to enable a coresight
path. If someone wants to really see the messages, they can always
enable it at runtime via dynam
6 matches
Mail list logo