Re: Call For Test: Powerd supported hwpstate_amd

Charlie Li <[email protected]>
Newsgroups gmane.os.freebsd.devel.hackers
Organization FreeBSD Project
Message-ID <[email protected]>
ShengYi Hung wrote:
> Dear all:
> 
> Sorry for the confusion caused by the earlier version of the | 
> hwpstate_amd| driver I shared last month.
> 
> I’ve prepared a new patch that adds |powerd| support for |hwpstate_amd|. 
> The patch is available here [1].
> 
> Please note that this patch depends on a series of parent patches, all 
> of which must be applied first. For convenience, I’ve created a GitHub 
> branch [2] that contains the complete patch series, so you can use |git 
> am| to apply them in order.
> 
> On my Framework 13 (7040 series), the legacy P-State driver exposes only 
> three frequency levels, which limits control granularity. In contrast, 
> the CPPC driver exposes 10 frequency levels (and potentially more), 
> allowing |powerd| to manage CPU performance with much finer granularity.
> 
> That said, this driver still needs wider testing across different Zen2+ 
> systems. I would greatly appreciate any additional testing and feedback.
> 
> Thanks!
> 
> [1]: https://reviews.freebsd.org/D55477
> 
> [2]: https://github.com/aokblast/freebsd-src/commits/hwpstate_amd/ 
> cpufreq_write/
> 
I would like to test on my Green Sardine/Cezanne/5000 series, but this 
no longer applies on latest main, especially after D55251 landed. I 
commented in the review where the conflicts happened, but I'm not sure 
if the rest of my rebase attempt made any sense considering the other 
changes of D55251.

-- 
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc (application/pgp-signature, 236 B)
-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTHxcCLnAXo3rFg6k7P+1cn7slqBAUCaZ9t+AUDAAAAAAAKCRDP+1cn7slqBKkp
AP9/iLk7vQ2+MO0DL/7VirjkNpbBkqFu1n7WH8IVu1NxfwD+PkyX5sfNdGjmKJCOwMtOX5np8JFo
q5ripP1axd05GQg=
=yGFx
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.