From: Wyes Karny <wyes.karny@amd.com>
To: Tor Vic <torvic9@mailbox.org>
Cc: Rafael J Wysocki <rafael@kernel.org>,
Huang Rui <ray.huang@amd.com>, Jonathan Corbet <corbet@lwn.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Mario.Limonciello@amd.com, Perry.Yuan@amd.com,
Ananth Narayan <ananth.narayan@amd.com>,
gautham.shenoy@amd.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
santosh.shukla@amd.com, Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH v3 0/6] amd_pstate: Add guided autonomous mode support
Date: Tue, 31 Jan 2023 05:34:27 +0000 [thread overview]
Message-ID: <20230131053427.cdpg5zaqyxf7ou2f@beas> (raw)
In-Reply-To: <8c09f806-b00d-515b-bd1d-2f433e44b1a4@mailbox.org>
Hi Tor Vic,
On 24 Jan 20:40, Tor Vic wrote:
--------------------------------->8-----------------------------
>
> The "active" mode seems to be broken here on a Zen2 3900X running Linux 6.1.
> Frequency remains stuck at minimum which is +-500 MHz.
I've fixed this in v4.
>
> Some queries of the new /sys devices lead to I/O error:
>
> # LANG=C cat /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_*
> 166
> cat:
> /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_lowest_nonlinear_freq:
> Input/output error
> cat: /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_max_freq:
> Input/output error
>
This issue I'm not able to reproduce. Is this issue seen with only EPP
patches also?
Could you please check if this issue still there with v4?
Thanks,
Wyes
> The "guided" mode seems to work fine with no stuck frequency, but also
> produces I/O error on some /sys files.
>
> I haven't tested "passive".
>
> Cheers,
>
> Tor Vic
next prev parent reply other threads:[~2023-01-31 5:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 11:50 [PATCH v3 0/6] amd_pstate: Add guided autonomous mode support Wyes Karny
2023-01-19 11:50 ` [PATCH v3 1/6] acpi: cppc: Add min and max perf reg writing support Wyes Karny
2023-01-19 11:50 ` [PATCH v3 2/6] acpi: cppc: Add auto select register read/write support Wyes Karny
2023-01-19 11:50 ` [PATCH v3 3/6] cpufreq: amd_pstate: Add guided autonomous mode Wyes Karny
2023-01-19 11:50 ` [PATCH v3 4/6] Documentation: amd_pstate: Move amd_pstate param to alphabetical order Wyes Karny
2023-01-19 11:50 ` [PATCH v3 5/6] cpufreq: amd_pstate: Add guided mode control support via sysfs Wyes Karny
2023-01-19 11:50 ` [PATCH v3 6/6] Documentation: amd_pstate: Update amd_pstate status sysfs for guided Wyes Karny
2023-01-19 12:30 ` Bagas Sanjaya
2023-01-20 4:16 ` Wyes Karny
2023-01-20 9:18 ` [PATCH v3 0/6] amd_pstate: Add guided autonomous mode support Huang Rui
2023-01-20 9:55 ` Wyes Karny
2023-01-24 20:40 ` Tor Vic
2023-01-25 10:25 ` Wyes Karny
2023-01-31 5:34 ` Wyes Karny [this message]
2023-02-01 18:15 ` Tor Vic
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=20230131053427.cdpg5zaqyxf7ou2f@beas \
--to=wyes.karny@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=ananth.narayan@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=robert.moore@intel.com \
--cc=santosh.shukla@amd.com \
--cc=torvic9@mailbox.org \
--cc=viresh.kumar@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).