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]
Date:   Thu, 30 Mar 2023 10:38:08 +0100
From:   Sudeep Holla <sudeep.holla@....com>
To:     Maulik Shah <quic_mkshah@...cinc.com>
Cc:     andersson@...nel.org, ulf.hansson@...aro.org,
        dianders@...omium.org, Sudeep Holla <sudeep.holla@....com>,
        swboyd@...omium.org, wingers@...gle.com,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-pm@...r.kernel.org, jwerner@...omium.org,
        quic_lsrao@...cinc.com, quic_rjendra@...cinc.com
Subject: Re: [PATCH v2 0/2] Use PSCI OS initiated mode for sc7280

On Thu, Mar 30, 2023 at 02:12:48PM +0530, Maulik Shah wrote:
> Changes in v2:
> - Add new change to Move enabling OSI mode after power domains creation
> - Fix compatible string to domains-idle-states for cluster idle state.
> - Update cover letter with some more details on OSI and PC mode comparision
> 
> The dependency [2] is now merged in trustedfirmware project.
> 
> Stats comparision between OSI and PC mode are captured at [3] with usecase
> details, where during multiple CPUs online the residency in cluster idle
> state is better with OSI and also inline with single CPU mode. In PC mode
> with multiple CPUs cluster idle state residency is dropping compare to
> single CPU mode.
> 
> Recording of this meeting is also available at [4].
> 
> This change adds power-domains for cpuidle states to use PSCI OS
> initiated mode for sc7280.
> 
> This change depends on external project changes [1] & [2] which are
> under review/discussion to add PSCI os-initiated support in Arm Trusted
> Firmware.
>

I will wait for your response to understand the issue in 1/2. If it is
firmware issue, I prefer we fix it in the firmware and no quirks or work
around for this in the kernel while it is still fresh out of oven.

-- 
Regards,
Sudeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ