From: Mel Gorman <mgorman@techsingularity.net>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: ACPI _CST introduced performance regresions on Haswll
Date: Wed, 7 Oct 2020 20:23:09 +0100 [thread overview]
Message-ID: <20201007192309.GO3227@techsingularity.net> (raw)
In-Reply-To: <172043a7-d180-292e-249b-7aea16c2209a@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
On Wed, Oct 07, 2020 at 05:40:43PM +0200, Rafael J. Wysocki wrote:
> > # grep . enable-cst/cpuidle/state*/disable
> > enable-cst/cpuidle/state0/disable:0
> > enable-cst/cpuidle/state1/disable:0
> > enable-cst/cpuidle/state2/disable:0
> > enable-cst/cpuidle/state3/disable:1
> > enable-cst/cpuidle/state4/disable:1
> > # grep . enable-cst/cpuidle/state*/default_status
> > enable-cst/cpuidle/state0/default_status:enabled
> > enable-cst/cpuidle/state1/default_status:enabled
> > enable-cst/cpuidle/state2/default_status:enabled
> > enable-cst/cpuidle/state3/default_status:disabled
> > enable-cst/cpuidle/state4/default_status:disabled
> >
> > That looks like C3 and C6 are disabled after the patch.
> >
> > # grep . enable-cst/cpuidle/state*/name
> > enable-cst/cpuidle/state0/name:POLL
> > enable-cst/cpuidle/state1/name:C1
> > enable-cst/cpuidle/state2/name:C1E
> > enable-cst/cpuidle/state3/name:C3
> > enable-cst/cpuidle/state4/name:C6
> >
>
> That's kind of unexpected and there may be two reasons for that.
>
> First off, the MWAIT hints in the ACPI tables for C3 and C6 may be different
> from the ones in the intel_idle internal table.
>
> Second, the ACPI tables may only be listing C1.
>
> Can you send me the acpidump output from the affected machine, please?
>
Attached.
Thanks.
--
Mel Gorman
SUSE Labs
[-- Attachment #2: acpidump.xz --]
[-- Type: application/x-xz, Size: 92724 bytes --]
prev parent reply other threads:[~2020-10-07 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 8:36 ACPI _CST introduced performance regresions on Haswll Mel Gorman
2020-10-06 16:00 ` Rafael J. Wysocki
2020-10-06 19:03 ` Mel Gorman
2020-10-06 19:29 ` Rafael J. Wysocki
2020-10-06 21:18 ` Mel Gorman
2020-10-07 15:45 ` Rafael J. Wysocki
2020-10-08 9:09 ` Mel Gorman
2020-10-08 17:15 ` Rafael J. Wysocki
2020-10-08 17:34 ` Mel Gorman
2020-10-13 18:55 ` Rafael J. Wysocki
2020-10-14 22:37 ` Mel Gorman
2020-10-15 18:34 ` Mel Gorman
2020-10-16 13:41 ` Rafael J. Wysocki
2020-10-16 14:09 ` Mel Gorman
2020-10-16 15:29 ` Rafael J. Wysocki
2020-10-06 19:47 ` Mel Gorman
2020-10-07 15:40 ` Rafael J. Wysocki
2020-10-07 19:23 ` Mel Gorman [this message]
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=20201007192309.GO3227@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).