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: Tue, 30 Nov 2021 18:50:17 +0800 [thread overview]
Message-ID: <YaYB6UoC1iqsNuJL@amd.com> (raw)
In-Reply-To: <CAHbf0-G7LEUuEtsh7XsK0Nv4xcKJQQbV9DAzUxxeJUvkhky9JA@mail.gmail.com>
On Fri, Nov 26, 2021 at 09:24:43PM +0800, Mike Lothian wrote:
> So
>
> 0 is my 6800M
>
> VCE feature version: 0, firmware version: 0x00000000
> UVD feature version: 0, firmware version: 0x00000000
> MC feature version: 0, firmware version: 0x00000000
> ME feature version: 40, firmware version: 0x00000040
> PFP feature version: 40, firmware version: 0x00000058
> CE feature version: 40, firmware version: 0x00000024
> RLC feature version: 1, firmware version: 0x00000044
> RLC SRLC feature version: 0, firmware version: 0x00000000
> RLC SRLG feature version: 0, firmware version: 0x00000000
> RLC SRLS feature version: 0, firmware version: 0x00000000
> MEC feature version: 40, firmware version: 0x0000005c
> MEC2 feature version: 40, firmware version: 0x0000005c
> SOS feature version: 0, firmware version: 0x0022020a
> ASD feature version: 553648226, firmware version: 0x21000062
> TA XGMI feature version: 0x00000000, firmware version: 0x00000000
> TA RAS feature version: 0x00000000, firmware version: 0x00000000
> TA HDCP feature version: 0x00000000, firmware version: 0x17000024
> TA DTM feature version: 0x00000000, firmware version: 0x1200000b
> TA RAP feature version: 0x00000000, firmware version: 0x0700000e
> TA SECUREDISPLAY feature version: 0x00000000, firmware version: 0x00000000
> SMC feature version: 0, firmware version: 0x00412e00 (65.46.0)
> SDMA0 feature version: 52, firmware version: 0x00000045
> SDMA1 feature version: 52, firmware version: 0x00000045
> VCN feature version: 0, firmware version: 0x02110001
> DMCU feature version: 0, firmware version: 0x00000000
> DMCUB feature version: 0, firmware version: 0x02020007
> TOC feature version: 0, firmware version: 0x00000000
> VBIOS version: SWBRT77321.001
>
> And 1 is the onboard graphics for the 5900HX
>
> VCE feature version: 0, firmware version: 0x00000000
> UVD feature version: 0, firmware version: 0x00000000
> MC feature version: 0, firmware version: 0x00000000
> ME feature version: 53, firmware version: 0x000000a6
> PFP feature version: 53, firmware version: 0x000000c0
> CE feature version: 53, firmware version: 0x0000004f
> RLC feature version: 1, firmware version: 0x0000003c
> RLC SRLC feature version: 1, firmware version: 0x00000001
> RLC SRLG feature version: 1, firmware version: 0x00000001
> RLC SRLS feature version: 1, firmware version: 0x00000001
> MEC feature version: 53, firmware version: 0x000001ce
> SOS feature version: 0, firmware version: 0x00000000
> ASD feature version: 0, firmware version: 0x21000064
> TA XGMI feature version: 0x00000000, firmware version: 0x00000000
> TA RAS feature version: 0x00000000, firmware version: 0x00000000
> TA HDCP feature version: 0x00000000, firmware version: 0x17000025
> TA DTM feature version: 0x00000000, firmware version: 0x1200000c
> TA RAP feature version: 0x00000000, firmware version: 0x00000000
> TA SECUREDISPLAY feature version: 0x00000000, firmware version: 0x00000000
> SMC feature version: 0, firmware version: 0x00402d00 (64.45.0)
Thanks for information. Could you please enable the trace event of
amd_pstate_perf before you run the test.
echo 1 > /sys/kernel/tracing/events/amd_cpu/enable
Then dump the traces with "cat /sys/kernel/debug/tracing/trace". We can
double confirm whether the amd-pstate driver program the correct
performance value in your processor.
Thanks,
Ray
next prev parent reply other threads:[~2021-11-30 10:50 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 [this message]
[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
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=YaYB6UoC1iqsNuJL@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.