The laptop hardware, firmware and current kernel supports persistent configuration of ACPI power_platform. If I boot into systemd.unit=rescue.target, do

echo new_value > /sys/firmware/acpi/platform_profile

and reboot, I can see new_value in UEFI configuration interface and when booting into systemd.unit=rescue.target again

cat /sys/firmware/acpi/platform_profile

displays new_value.

So I assume that this is behavior desired by laptop manufacturerand and expected by laptop users. When user shuts down system and tuned service is running it rolls back /sys/firmware/acpi/platform_profile value, overriding most recent user selection done through DE and tuned-ppd. Settings rollback=not_on_exit in /etc/tuned/tuned-main.conf does not help.

This has been discovered when investigating (https://discussion.fedoraproject.org/t/offline-upgrades-and-power-management/202208) why most recent power configuration selected by user through DE is not applied during offline upgrades (https://fedoraproject.org/wiki/Features/OfflineSystemUpdates). Having this parameter value persist may improve user experience during modetate+sized offline upgrades, but it is not going to help if system doesn't support ACPI power_platform configuration. Should user power profile selection through DE influence offline upgrades and akmods service? Other stages of boot process?

Reproducible: Always

Steps to Reproduce:
1. Boot stock Fedora Workstation into graphical.target, noting current ACPI power_profile value in UEFI configuration interface
2. Set rollback=not_on_exit in /etc/tuned/tuned-main.conf and restart tuned
3. Change desktop power profile to one with different acpi.platform_profile value
4. Reboot and check current ACPI power_profile value in UEFI configuration interface
Actual Results:
ACPI power_profile value in step 4 matches step 1

Expected Results:
ACPI power_profile value in step 4 matches selected profile value in step 3