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: <c7d1eced-d77b-aca7-1422-6eefaf704f3e@gmail.com>
Date:   Sat, 19 Aug 2023 21:41:36 +0200
From:   Guillaume Martres <smarter3@...il.com>
To:     "Zhang, Rui" <rui.zhang@...el.com>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "jacob.jun.pan@...ux.intel.com" <jacob.jun.pan@...ux.intel.com>,
        "noltari@...il.com" <noltari@...il.com>,
        "lenb@...nel.org" <lenb@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:     "Bityutskiy, Artem" <artem.bityutskiy@...el.com>
Subject: Re: [PATCH] intel_idle: Add RaptorLake support

On 1/19/23 17:13, Zhang, Rui wrote:
> On Thu, 2023-01-19 at 08:02 +0100, Álvaro Fernández Rojas wrote:
>> This patch adds RaptorLake support to the intel_idle driver.
>>
>> Since RaptorLake and AlderLake C-state are characteristics the same,
>> we use
>> AlderLake C-states tables for RaptorLake as well.
> 
> RPL and ADL have same cstates and use the same mwait hints, but the
> latency of each c-state are still different on different platforms.
> So we can not just duplicate the ADL table on RPL.
> 
> There is an effort ongoing that measures the latency of each
> cstate on the RPL platforms. And based on the measurement result, we
> can decide if a new custom table is needed or we can just copy the
> previous platform. Hopefully we will have a patch in a couple of weeks.

Hi, I just stumbled upon this patch series as I was wondering about the
lack of support for Raptor Lake in intel_idle. Your last message from
January mentions a future patch, is it available anywhere or is this
still future work?

Thank you,
Guillaume

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ