From: Huang Rui <ray.huang@amd.com>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: "Du, Xiaojian" <Xiaojian.Du@amd.com>,
Linux PM list <linux-pm@vger.kernel.org>,
"Su, Jinzhou (Joe)" <Jinzhou.Su@amd.com>
Subject: Re: AMD Pstate
Date: Fri, 3 Dec 2021 11:27:11 +0800 [thread overview]
Message-ID: <YamOj5ica/GY82gu@amd.com> (raw)
In-Reply-To: <CAHbf0-HBag=RBi_=FJ==0CGxsF456y3M13EvhtGpsuxc=+AtEQ@mail.gmail.com>
On Fri, Dec 03, 2021 at 09:08:14AM +0800, Mike Lothian wrote:
> On Wed, 1 Dec 2021 at 06:51, Huang Rui <ray.huang@amd.com> wrote:
> >
> > On Wed, Dec 01, 2021 at 01:40:52PM +0800, Mike Lothian wrote:
> > > I've just tested v5 of the patchset, the warnings are gone, kconfig
> > > looks good and shedutil seems to be behaving
> > > Would it still be useful to get the above trace?
> >
> > Is the previous issue that the cpu clock stuck on 1 GHz still existed on
> > V5?
> >
> > Thanks,
> > Ray
> >
>
> Hi
>
> No the issue appears to be resolved, schedutil is now going to the
> maximum frequency - it appears to be behaving now
>
Good to hear that, thanks!
Ray
prev parent reply other threads:[~2021-12-03 3:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 10:37 AMD Pstate Mike Lothian
2021-11-21 11:52 ` Huang Rui
2021-11-21 12:35 ` Huang Rui
2021-11-23 10:47 ` Mike Lothian
2021-11-23 11:17 ` Huang Rui
2021-11-23 11:22 ` Mike Lothian
2021-11-23 11:32 ` Huang Rui
2021-11-24 0:17 ` Mike Lothian
[not found] ` <YZ22dYQ8dgQTwqnh@amd.com>
[not found] ` <CAHbf0-FnFpkmZ2bkfS2S=Cw_RLbK1y7eSHySAFGVecs+t+-aVg@mail.gmail.com>
2021-11-26 10:50 ` Mike Lothian
2021-11-26 11:32 ` Du, Xiaojian
2021-11-26 13:24 ` Mike Lothian
2021-11-30 10:50 ` Huang Rui
[not found] ` <CAHbf0-EWVeD8xehHZc8ff-4vYbXC69z=kMf0_=RXJsHKG_2M7Q@mail.gmail.com>
2021-12-01 6:51 ` Huang Rui
2021-12-03 1:08 ` Mike Lothian
2021-12-03 3:27 ` Huang Rui [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=YamOj5ica/GY82gu@amd.com \
--to=ray.huang@amd.com \
--cc=Jinzhou.Su@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=linux-pm@vger.kernel.org \
--cc=mike@fireburn.co.uk \
/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.