[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210513104555.GC1621127@hr-amd>
Date: Thu, 13 May 2021 18:45:55 +0800
From: Huang Rui <ray.huang@....com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Alexander Monakov <amonakov@...ras.ru>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Deucher, Alexander" <Alexander.Deucher@....com>,
Jason Bagavatsingham <jason.bagavatsingham@...il.com>,
"Pierre-Loup A . Griffais" <pgriffais@...vesoftware.com>,
"Fontenot, Nathan" <Nathan.Fontenot@....com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Borislav Petkov <bp@...e.de>,
"x86@...nel.org" <x86@...nel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH v4] x86, sched: Fix the AMD CPPC maximum perf on some
specific generations
On Thu, May 13, 2021 at 06:39:08PM +0800, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@...nel.org> wrote:
>
> > No need to send v5, done!
> >
> > I have a system that appears to be affected by this bug:
> >
> > kepler:~> lscpu | grep -i mhz
> > CPU MHz: 4000.000
> > CPU max MHz: 7140.6250
> > CPU min MHz: 2200.0000
> >
> > So I should be able to confirm after a reboot.
>
> 'CPU max Mhz' seems to be saner now:
>
> kepler:~> lscpu | grep -i mhz
>
> CPU MHz: 2200.000
> CPU max MHz: 4917.9678
> CPU min MHz: 2200.0000
>
Yes, happy to know this :-)
Thanks,
Ray
Powered by blists - more mailing lists