All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: 'Chen Yu' <yu.c.chen@intel.com>, linux-acpi@vger.kernel.org
Cc: linux-pm@vger.kernel.org,
	"'Rafael J. Wysocki'" <rafael@kernel.org>,
	'Len Brown' <lenb@kernel.org>
Subject: RE: [PATCH 0/2][RFC] ACPI / PM: Disable MSR T-state after resumed
Date: Fri, 25 Aug 2017 14:40:19 -0700	[thread overview]
Message-ID: <001b01d31dea$c116dc50$434494f0$@net> (raw)
In-Reply-To: lHgGdsvEp8Qk9lHgId179V

On 2017.08.25 09:43 Chen Yu wrote:

> There is a growing number of reports that the MSR throttling has
> been enabled after resumed back from suspend to ram, which impacts
> the system performance. This patchset tries to address this issue
> by turning off the T-state after resumed back.
>
> Chen Yu (2):
>  ACPI / PM: Reuse the acpi_sleep_syscore_ops for future requirement
>  ACPI / PM: Disable the MSR T-state during CPU online
>
> drivers/acpi/sleep.c | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 58 insertions(+), 2 deletions(-)

Hi Chen,

I'll just copy and paste what I wrote in a couple of the bug reports ([1] for example) a couple of days ago:

> I believe that pending changes to the intel-pstate CPU frequency scaling driver,
> proposed by Rafael, I think for kernel 4.14-rc1, will eliminate the ongoing
> troubles with Clock Modulation and the driver.
>
> I'm saying that the issue will no longer exist, and that the intel_pstate
> CPU frequency scaling driver will respond "properly" to Clock Modulation events.
> Of course, I'll check when kernel 4.14-rc1 becomes available, or before if I can
> apply all the patches.
>
> For reference see the patch set related to:
>
> [PATCH 0/2] cpufreq: intel_pstate: Eliminate the PID controller
> 2017.07.24 03:22 (or 10:22 UTC, I think)
>
> https://marc.info/?l=linux-pm&m=150093486908759&w=2
> https://marc.info/?l=linux-pm&m=150093484308751&w=2
> https://marc.info/?l=linux-pm&m=150093486808758&w=2

[1] https://bugzilla.kernel.org/show_bug.cgi?id=189861

             reply	other threads:[~2017-08-25 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 21:40 Doug Smythies [this message]
2017-08-26  6:08 ` [PATCH 0/2][RFC] ACPI / PM: Disable MSR T-state after resumed Chen Yu
2017-08-26 14:26 ` Doug Smythies
2017-08-26 16:07   ` Chen Yu
2017-08-27 18:52   ` Doug Smythies
  -- strict thread matches above, loose matches on Subject: below --
2017-08-25 16:43 Chen Yu

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='001b01d31dea$c116dc50$434494f0$@net' \
    --to=dsmythies@telus.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=yu.c.chen@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.