Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 591448 - Performance degradation with AMD PhenomII X6 Turbo-Core feature
Performance degradation with AMD PhenomII X6 Turbo-Core feature
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-12 05:43 EDT by Andre Przywara
Modified: 2010-06-03 04:06 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-20 23:49:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andre Przywara 2010-05-12 05:43:30 EDT
Description of problem:
AMD's Six-Core processor have a Turbo-Core feature automatically activated without software involvement. Due to a conflict with the powernow-k8 driver this feature is not activated under recent Linux kernel versions, resulting in bad performance.

Version-Release number of selected component (if applicable):
all Linux kernels starting from 2.6.30, including the Fedora13 version

How reproducible:
Do performance testing with AMD's desktop Six-Core processors featuring Turbo-Core (PhenomII X6 1090T and 1055T). Compare the performance to that with the Cool'n'Quiet _disabled_ in the BIOS.

Steps to Reproduce:
1. Boot Fedora13 on an AMD PhenomII X6 processor
2. Do some performance testing
3. Disable Cool'n'Quiet feature in the BIOS
4. Repeat performance testing, compare numbers to that of Step2
Actual results:
Performance with C'n'Q enabled is worse than with C'n'Q disabled.

Expected results:
Performance with C'n'Q enabled should be equal or better compared to C'n'Q disabled.

Additional info:
Following online articles describe the problem:
Comment 1 Andre Przywara 2010-05-12 05:48:46 EDT
The appropriate fix (a one-liner):
is already in 2.6.34-rc7 and will trickle down into stable soon.
Please cherry-pick this one into the Fedora13 release kernel.

Note You need to log in before you can comment on or make changes to this bug.