lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80e9fc21-cf1b-4118-52d5-7268f5470d1c@arm.com>
Date:   Mon, 3 Jun 2019 11:12:05 +0100
From:   Suzuki K Poulose <suzuki.poulose@....com>
To:     mike.leach@...aro.org
Cc:     linux-arm-kernel@...ts.infradead.org, coresight@...ts.linaro.org,
        linux-kernel@...r.kernel.org, mathieu.poirier@...aro.org
Subject: Re: [PATCH v4 26/30] coresight: Use platform agnostic names

Hi Mike,

On 29/05/2019 10:32, Mike Leach wrote:
> Hi,
> 
> Why am I not seeing references to coresight-cpu-debug in here? In
> other places in this patchset CPU debug has been changed, but there
> appears to be no platform agnostic name here, nor any ACPI type name
> either. Is cpu-debug remaining device tree only? Should CPU debug not
> be treated like ETM and get a cpu centric name?

Thats because they are not registered as coresight devices and thus do
not appear on the CoreSight bus under /sys/bus/coresight/. This set is
only tuning the "coresight" device names, linked to the real amba device.

Cheers
Suzuki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ