From: "Zhang, Rui" <rui.zhang@intel.com>
To: "smarter3@gmail.com" <smarter3@gmail.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>,
"noltari@gmail.com" <noltari@gmail.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>,
"Kumar, Vinay" <vinay.kumar@intel.com>
Subject: Re: [PATCH] intel_idle: Add RaptorLake support
Date: Sun, 20 Aug 2023 09:20:32 +0000 [thread overview]
Message-ID: <7e2c1da24b48217045e8ad95b739ec96cdce5931.camel@intel.com> (raw)
In-Reply-To: <c7d1eced-d77b-aca7-1422-6eefaf704f3e@gmail.com>
On Sat, 2023-08-19 at 21:41 +0200, Guillaume Martres wrote:
> 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.
intel_idle support for RaptorLake, and also other platforms that don't
have a custom table, is always there as long as we have BIOS support.
The custom table is just an optimization.
> Your last message from
> January mentions a future patch, is it available anywhere or is this
> still future work?
>
This is still work in progress because there are still some open
questions that we cannot answer from our measurement, and the table is
not finalized yet.
thanks,
rui
next prev parent reply other threads:[~2023-08-20 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 7:02 [PATCH] intel_idle: Add RaptorLake support Álvaro Fernández Rojas
2023-01-19 7:52 ` Zhang, Rui
2023-01-19 13:26 ` Rafael J. Wysocki
2023-01-19 16:13 ` Zhang, Rui
2023-08-19 19:41 ` Guillaume Martres
2023-08-20 9:20 ` Zhang, Rui [this message]
2023-08-20 10:28 ` Guillaume Martres
2023-08-24 6:30 ` Zhang, Rui
2024-04-07 17:37 ` László Péter
2024-04-08 2:01 ` Zhang, Rui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e2c1da24b48217045e8ad95b739ec96cdce5931.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=artem.bityutskiy@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=smarter3@gmail.com \
--cc=vinay.kumar@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox