1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

A Proper Solution To The Linux ASPM Problem

Michael Larabel

Published on 11 November 2011
Written by Michael Larabel
Page 2 of 3 - 40 Comments

Below is Matthew Garrett's description about this new patch.

Right now we forcibly clear ASPM state on all devices if the BIOS indicates that the feature is not supported. Based on the Microsoft presentation "PCI Express In Depth for Windows Vista and Beyond", I'm starting to think that this may be an error. The implication is that unless the platform grants full control via _OSC, Windows will not touch any PCIe features - including ASPM. In that case clearing ASPM state would be an error unless the platform has granted us that control.

This patch reworks the ASPM disabling code such that the actual clearing of state is triggered by a successful handoff of PCIe control to the OS. The general ASPM code undergoes some changes in order to ensure that the ability to clear the bits isn't overridden by ASPM having already been disabled. Further, this theoretically now allows for situations where only a subset of PCIe roots hand over control, leaving the others in the BIOS state.

It's difficult to know for sure that this is the right thing to do - there's zero public documentation on the interaction between all of these components. But enough vendors enable ASPM on platforms and then set this bit that it seems likely that they're expecting the OS to leave them alone.

Measured to save around 5W on an idle Thinkpad X220.

This ~60 line kernel patch changes the ASPM behavior and from his testing, plus my initial testing, it seems to be relatively sane. From the various notebooks (a half-dozen so far) I have been trying out, there have not been any problems and ASPM is working without having to manually force it.

On the next page is a test of this patch and the system power consumption from one of the ASPM affected systems under the Linux 2.6.37, 2.6.38, 3.2, and 3.2 patched kernels.

Latest Articles & Reviews
  1. Samsung 850 EVO SSD Linux Benchmarks
  2. Kubuntu 15.04 Is Turning Out Quite Nice, Good Way To Try Out The Latest KDE
  3. 5-Way Linux Distribution Comparison On The Core i3 NUC
  4. OCZ ARC 100 Linux SSD Benchmarks
  5. Lenovo ThinkPad X1 Carbon Works Great As A Linux Ultrabook
  6. Transcend SSD370 256GB
Latest Linux News
  1. New Specifications On The Alleged Ubuntu Tablet
  2. LLVM 3.6 Officially Released With Many Compiler Advantages
  3. VLC 2.2 "Weathermax" Brings Better VP9 & H.265 Support
  4. Open-Source .NET On Linux Continues Maturing
  5. Features Coming For The Imminent Xfce 4.12 Release
  6. Canonical's Latest Demo Of Ubuntu Unity 8 Convergence In Action
  7. The Quest For Decent, Low-Priced Server Cases & Racks/Cabinets
  8. Mesa 10.5 Is In Ubuntu 15.04 For The Latest Open-Source GPU Drivers
  9. ALSA 1.0.29 Released
  10. Ubuntu 15.04 Beta Released, Ubuntu MATE Made Official
Most Viewed News This Week
  1. Linux 4.0-RC1 Tagged, Linux 4.0 Will Bring Many Notable Improvements
  2. Screenshots Of The GNOME 3.16 Changes
  3. More Proof That Allwinner Is Violating The GPL
  4. Linux 4.0 Doesn't Have The Weirdest Codename
  5. Mir Now Depends Upon C++14
  6. GNOME 3.16 Beta Brings Wayland-Based Log-in Screen
  7. LLVM Clang Compiling The Linux Kernel Is A Big Topic For 2015
  8. Canonical Comes Up With Its Own FUSE Filesystem For Linux Containers
%%CLICK_URL_UNESC%%