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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200820162738.33053904@oasis.local.home>
Date:   Thu, 20 Aug 2020 16:27:38 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Peiyong Lin <lpy@...gle.com>
Cc:     amit.kucheria@...aro.org, android-kernel@...gle.com,
        gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
        mingo@...hat.com, paul.walmsley@...ive.com, pavel@....cz,
        prahladk@...gle.com, rafael.j.wysocki@...el.com,
        ulf.hansson@...aro.org, yamada.masahiro@...ionext.com,
        zzyiwei@...roid.com, sidaths@...gle.com
Subject: Re: [PATCH v3] Add power/gpu_frequency tracepoint.

On Thu, 20 Aug 2020 12:41:34 -0700
Peiyong Lin <lpy@...gle.com> wrote:

> Historically there is no common trace event for GPU frequency, in
> downstream Android each different hardware vendor implements their own
> way to expose GPU frequency, for example as a debugfs node.  This patch
> standardize it as a common trace event in upstream linux kernel to help
> the ecosystem have a common implementation across hardware vendors.
> Toolings in the Linux ecosystem will benefit from this especially in the
> downstream Android, where this information is critical to graphics
> developers.
> 
> Signed-off-by: Peiyong Lin <lpy@...gle.com>

Just from the tracing point of view (not from the content of the trace
point of view).

Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ