From: Artem Bityutskiy <dedekind1@gmail.com>
To: Guilhem Lettron <guilhem@barpilot.io>, Zhang Rui <rui.zhang@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>, Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] intel_idle: Add ICL support
Date: Wed, 26 Aug 2020 19:19:35 +0300 [thread overview]
Message-ID: <72fab2376722c6169549669016933217d3da34a0.camel@gmail.com> (raw)
In-Reply-To: <CAGX5Wg0=K5AaTut5KH3R3+oasM5MM7PaJ9Z_L56xSNckMbWC9g@mail.gmail.com>
Indeed, when I compare them:
acpi_idle (without the patch):
CPU%c1 CPU%c6 CPU%c7 CoreTmp PkgTmp GFX%rc6 Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 PkgWatt
29.48 0.00 60.71 58 58 97.96 16.96 0.00 0.00 0.00 0.00 0.00 0.00 6.08
intel_idle (with the patch):
CPU%c1 CPU%c6 CPU%c7 CoreTmp PkgTmp GFX%rc6 Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 PkgWatt
56 56 96.64 300 68.29 48.58 0.00 0.00 0.00 0.00 0.00 0.00 7.38 0.00
With intel_idle we reach PC10, without it we only go as deep as PC2 - huge difference.
I really wonder why the BIOS does not expose deeper C-states... And if
it does not, is this for a reason? And how windows works then?
May be there is a BIOS update that fixes this problem? May be Windows
user get it quickly because stuff like this is often well-integrated in
Windows? Would you please check if there is newer BIOS?
Artem.
next prev parent reply other threads:[~2020-08-26 16:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 12:04 [PATCH] intel_idle: Add ICL support Guilhem Lettron
2020-08-26 12:43 ` Rafael J. Wysocki
2020-08-26 13:03 ` Guilhem Lettron
2020-08-26 13:09 ` Artem Bityutskiy
2020-08-26 13:19 ` Guilhem Lettron
2020-08-26 13:20 ` Rafael J. Wysocki
2020-08-26 13:16 ` Artem Bityutskiy
2020-08-26 13:18 ` Artem Bityutskiy
2020-08-26 13:21 ` Rafael J. Wysocki
2020-08-26 13:32 ` Guilhem Lettron
2020-08-26 13:41 ` Zhang Rui
2020-08-26 14:04 ` Guilhem Lettron
2020-08-26 16:02 ` Rafael J. Wysocki
2020-08-26 16:21 ` Rafael J. Wysocki
2020-08-26 16:39 ` Artem Bityutskiy
2020-08-26 16:43 ` Rafael J. Wysocki
2020-08-26 16:46 ` Guilhem Lettron
2020-08-26 17:00 ` Rafael J. Wysocki
2020-08-26 17:47 ` Zhang Rui
2020-08-26 16:52 ` Artem Bityutskiy
2020-08-26 16:19 ` Artem Bityutskiy [this message]
2020-08-26 16:25 ` Artem Bityutskiy
2020-08-26 16:28 ` Artem Bityutskiy
2020-08-26 16:41 ` Rafael J. Wysocki
[not found] ` <CAGX5Wg0655U71nFcaAJXmj1XMA3MjnCVn=q1Pf=7LLyryHhroQ@mail.gmail.com>
2020-08-26 13:17 ` Rafael J. Wysocki
2020-08-26 13:34 ` Guilhem Lettron
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=72fab2376722c6169549669016933217d3da34a0.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=guilhem@barpilot.io \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.