From: "Zhang, Rui" <rui.zhang@intel.com>
To: "kai.heng.feng@canonical.com" <kai.heng.feng@canonical.com>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>,
"lenb@kernel.org" <lenb@kernel.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] intel_idle: Add Jasper Lake and Elkhart Lake support
Date: Fri, 26 Jul 2024 06:51:54 +0000 [thread overview]
Message-ID: <2048df524f8be7ed200bc92eb1c6efe106f0ed19.camel@intel.com> (raw)
In-Reply-To: <20240726062601.674078-1-kai.heng.feng@canonical.com>
On Fri, 2024-07-26 at 14:26 +0800, Kai-Heng Feng wrote:
> Without proper C-state support, the CPU can take long time to exit to
> C0
> to handle IRQ and perform DMA.
Can you provide more details?
Say, what cstate is entered w/ and w/o this patch?
can you show the output of "grep .
/sys/devices/system/cpu/cpu0/cpuidle/state*/*" without this patch?
>
> The data collect via wult shows the latency is similar to Broxton, so
> use the existing table to support C-state on JSL and EHL.
so you have done cstate measurement on the EHL using wult?
can you share more details about the measurement results?
thanks,
rui
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=219023
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
> drivers/idle/intel_idle.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> index 9aab7abc2ae9..eb6975a1d083 100644
> --- a/drivers/idle/intel_idle.c
> +++ b/drivers/idle/intel_idle.c
> @@ -1538,6 +1538,8 @@ static const struct x86_cpu_id intel_idle_ids[]
> __initconst = {
> X86_MATCH_VFM(INTEL_ATOM_GOLDMONT, &idle_cpu_bxt),
> X86_MATCH_VFM(INTEL_ATOM_GOLDMONT_PLUS, &idle_cpu_bxt),
> X86_MATCH_VFM(INTEL_ATOM_GOLDMONT_D, &idle_cpu_dnv),
> + X86_MATCH_VFM(INTEL_ATOM_TREMONT, &idle_cpu_bxt),
> + X86_MATCH_VFM(INTEL_ATOM_TREMONT_L, &idle_cpu_bxt),
> X86_MATCH_VFM(INTEL_ATOM_TREMONT_D, &idle_cpu_snr),
> X86_MATCH_VFM(INTEL_ATOM_CRESTMONT, &idle_cpu_grr),
> X86_MATCH_VFM(INTEL_ATOM_CRESTMONT_X, &idle_cpu_srf),
next prev parent reply other threads:[~2024-07-26 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 6:26 [PATCH] intel_idle: Add Jasper Lake and Elkhart Lake support Kai-Heng Feng
2024-07-26 6:51 ` Zhang, Rui [this message]
2024-07-26 6:54 ` Zhang, Rui
2024-07-29 4:07 ` Kai-Heng Feng
2024-07-30 13:59 ` Rafael J. Wysocki
2024-07-31 6:17 ` Kai-Heng Feng
2024-07-31 16:28 ` Len Brown
2024-08-01 6:54 ` Kai-Heng Feng
2024-08-01 10:20 ` Rafael J. Wysocki
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=2048df524f8be7ed200bc92eb1c6efe106f0ed19.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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