diff options
author | Robert Richter <robert.richter@amd.com> | 2011-11-08 19:20:44 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2011-12-05 09:32:59 +0100 |
commit | 16e5294e5f8303756a179cf218e37dfb9ed34417 (patch) | |
tree | 7245aa1580ae7658d806057199ffad4b8d9d9e37 /include | |
parent | 6a600a8b8749566a7d81ad75dcb8bf5342b5a39a (diff) | |
download | linux-stable-16e5294e5f8303756a179cf218e37dfb9ed34417.tar.gz linux-stable-16e5294e5f8303756a179cf218e37dfb9ed34417.tar.bz2 linux-stable-16e5294e5f8303756a179cf218e37dfb9ed34417.zip |
perf, x86: Force IBS LVT offset assignment for family 10h
On AMD family 10h we see firmware bug messages like the following:
[Firmware Bug]: cpu 6, try to use APIC500 (LVT offset 0) for vector 0x10400, but the register is already in use for vector 0xf9 on another cpu
[Firmware Bug]: cpu 6, IBS interrupt offset 0 not available (MSRC001103A=0x0000000000000100)
[Firmware Bug]: using offset 1 for IBS interrupts
[Firmware Bug]: workaround enabled for IBS LVT offset
perf: AMD IBS detected (0x00000007)
We always see this, since the offsets are not assigned by the BIOS for
this family. Force LVT offset assignment in this case. If the OS
assignment fails, fallback to BIOS settings and try to setup this.
The fallback to BIOS settings weakens the family check since
force_ibs_eilvt_setup() may fail e.g. in case of virtual machines.
But setup may still succeed if BIOS offsets are correct.
Other families don't have a workaround implemented that assigns LVT
offsets. It's ok, to drop calling force_ibs_eilvt_setup() for that
families.
With the patch the [Firmware Bug] messages vanish. We see now:
IBS: LVT offset 1 assigned
perf: AMD IBS detected (0x00000007)
Signed-off-by: Robert Richter <robert.richter@amd.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/20111109162225.GO12451@erda.amd.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions