linux-kernel - RE: [PATCH] [v4] x86, suspend: Save/restore extra MSR registers for suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 1 Nov 2015 16:49:40 +0000
From:	"Chen, Yu C" <yu.c.chen@...el.com>
To:	Doug Smythies <dsmythies@...us.net>
CC:	"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"hpa@...or.com" <hpa@...or.com>, "bp@...en8.de" <bp@...en8.de>,
	"Zhang, Rui" <rui.zhang@...el.com>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Brown, Len" <len.brown@...el.com>,
	"'Ingo Molnar'" <mingo@...nel.org>, 'Pavel Machek' <pavel@....cz>,
	"'Kristen Carlson Accardi'" <kristen@...ux.intel.com>,
	"Pandruvada, Srinivas" <srinivas.pandruvada@...el.com>
Subject: RE: [PATCH] [v4] x86, suspend: Save/restore extra MSR registers for
 suspend

Hi, Doug,
Sorry for my late response, and thanks for your information:

> -----Original Message-----
> From: Doug Smythies [mailto:dsmythies@...us.net]
> Sent: Sunday, October 11, 2015 11:47 PM
> To: Chen, Yu C
> Cc: Wysocki, Rafael J; tglx@...utronix.de; hpa@...or.com; bp@...en8.de;
> Zhang, Rui; linux-pm@...r.kernel.org; x86@...nel.org; linux-
> kernel@...r.kernel.org; Brown, Len; 'Ingo Molnar'; 'Pavel Machek'; 'Kristen
> Carlson Accardi'; Doug Smythies
> Subject: RE: [PATCH] [v4] x86, suspend: Save/restore extra MSR registers for
> suspend
> 
> Hi Yu, thanks for your reply.
> 
> On 2015.10.10 19:27 Chen, Yu C wrote:
> > On 2105.10.10 02:56 Doug Smythies wrote:
> >
> >>> The current version of the intel_pstate driver is incompatible with
> >>> any use of Clock Modulation, always resulting in driving the target
> >>> pstate to the minimum, regardless of load. The result is the
> >>> apparent CPU frequency stuck at minimum * modulation percent.
> >>
> >>> The acpi-cpufreq driver works fine with Clock Modulation, resulting
> >>> in desired frequency * modulation percent.
> >>
> 
> > [Yu] Why intel_pstate driver is incompatible with Clock Modulation?
> 
> It is simply how the current control algorithm responds to the scenario.
> 
> The problem is in intel_pstate_get_scaled_busy, here:
> 
>         /*
>          * core_busy is the ratio of actual performance to max
>          * max_pstate is the max non turbo pstate available
>          * current_pstate was the pstate that was requested during
>          *      the last sample period.
>          *
>          * We normalize core_busy, which was our actual percent
>          * performance to what we requested during the last sample
>          * period. The result will be a percentage of busy at a
>          * specified pstate.
>          */
>         core_busy = cpu->sample.core_pct_busy;
>         max_pstate = int_tofp(cpu->pstate.max_pstate);
>         current_pstate = int_tofp(cpu->pstate.current_pstate);
>         core_busy = mul_fp(core_busy, div_fp(max_pstate, current_pstate));
> 
> With Clock Modulation enabled, the actual performance percent will always
> be less than what was asked for, basically meaning current_pstate is much
> less than what was asked for. Thus the algorithm will drive down the target
> pstate regardless of load.
> 
[Yu] Do you mean, there is some problem with the normalization,and we should use 
the actual pstate rather than the theoretical current_pstate, for example, 
the pseudocode might looked like:

-  current_pstate = int_tofp(cpu->pstate.current_pstate);
+ current_pstate = int_tofp(cpu->pstate.current_pstat)*0.85;

Best Regards,
Yu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/