Hi, Do you have news about this subject? I used to use TLP on my T450s, i have instal it in dom0 but i think there is more thing to do with qubes?
For lenovo T4x owner, I plan to install kernel-devel and install kmod acpi_call from rpmfusion to be able to set battery thresholds, very usefull for his life. I'm interested, If I can help, doing some test, say me :) Le mardi 19 janvier 2016 20:04:39 UTC+1, Ivan a écrit : > > Hi list, > > After years of using stock fedora as my main OS, I migrated to Qubes a > few weeks ago and I'm really happy I made the switch. Kudos to devs and > contributors ! > > The only minus compared to my former fedora install is the increased > power consumption when running on battery. With casual browsing, no CPU > intensive task, I remember I was using around 4.5 - 5W (on a thinkpad > T450s with high end specs). With the same work pattern/panel > backlight/... in Qubes, I'm at 7+ W. A power increase is of course > expected given the overhead of virtualization, but it looks like some > things can be improved. For instance: > > - enabling usb autosuspend in sys-usb and power savings for the wireless > adapter in sys-net saves aroud 0.5W (just as I'm typing that email, I'm > at 6.6W after those tweaks, compared to ~7.2W before). > - then, enabling various other power saving features in dom0 saves > another 0.6-0.7W. I hand picked the scripts from tlp [1] since > installing it from rpm in dom0 would require installing a lot of > dependencies / uneeded stuff. > > Those 2 things saved almost 1.2W with no noticeable decrease in > performance (at least for me - YMMV). Automating this in Qubes should be > pretty straightforward: > - pull TLP and its dependencies in dom0, or create a set of Qubes > specific similar power saving scripts. > - install TLP in template VMs > - on BAT/AC event, add a udev rule in dom0 that would qvm-run "tlp bat" > in guest vms. > > By the way I noticed that the IA32_ENERGY_PERF_BIAS MSR power saving > feature didn't work (it used to worked on that laptop with stock f22): > > in dom0: > > sudo x86_energy_perf_policy performance > sudo x86_energy_perf_policy -r > cpu0: 0x0000000000000000 > cpu1: 0x0000000000000000 > cpu2: 0x0000000000000000 > cpu3: 0x0000000000000000 > > sudo x86_energy_perf_policy powersave > sudo x86_energy_perf_policy -r > cpu0: 0x0000000000000000 > cpu1: 0x0000000000000000 > cpu2: 0x0000000000000000 > cpu3: 0x0000000000000000 > > ie, it's stuck in performance mode and can't be changed. I remember the > grsec patches exhibited the same problem since writing to MSRs was > disabled altogether. Is that the same with Qubes ? If yes, maybe make an > exception for that specific register ? (By the way I haven't made a > power consumption comparison when enabling/disabling that feature on > stock fedora, maybe it's negligible). > > There are probably other features that could be helpful provided they > are enabled in Qubes' kernel, eg. the upcoming reworked intel PSR > feature for intel cards and panels that support it (like in newer > thinkpads). I'm also wondering how/if setting power saving features in > guests other than hardware (eg. vm/disk stuff) would impact power > consumption - I didn't have time to research that yet. > > I'd be happy to help if people are interested. Tests, power consumption > figures, scripts/udev rules, ... > > Cheers, > ivan > > > [1] http://linrunner.de/en/tlp/tlp.html > -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/bfbb0cdf-4e00-47a1-9c57-0f390af3df7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
