diff options
author | Andre Przywara <andre.przywara@amd.com> | 2012-06-01 16:52:37 +0200 |
---|---|---|
committer | H. Peter Anvin <hpa@zytor.com> | 2012-06-07 11:43:30 -0700 |
commit | 169e9cbd77db23fe50bc8ba68bf081adb67b4220 (patch) | |
tree | befeef8f305e9d16852dd27d18fdbbf1ef85a31d /samples/trace_events | |
parent | ecd431d95aa04257e977fd6878e4203ce462e7e9 (diff) | |
download | blackbird-op-linux-169e9cbd77db23fe50bc8ba68bf081adb67b4220.tar.gz blackbird-op-linux-169e9cbd77db23fe50bc8ba68bf081adb67b4220.zip |
x86, cpu, amd: Fix crash as Xen Dom0 on AMD Trinity systems
f7f286a910221 ("x86/amd: Re-enable CPU topology extensions in case BIOS
has disabled it") wrongfully added code which used the AMD-specific
{rd,wr}msr variants for no real reason.
This caused boot panics on xen which wasn't initializing the
{rd,wr}msr_safe_regs pv_ops members properly.
This, in turn, caused a heated discussion leading to us reviewing all
uses of the AMD-specific variants and removing them where unneeded
(almost everywhere except an obscure K8 BIOS fix, see 6b0f43ddfa358).
Finally, this patch switches to the standard {rd,wr}msr*_safe* variants
which should've been used in the first place anyway and avoided unneeded
excitation with xen.
Signed-off-by: Andre Przywara <andre.przywara@amd.com>
Link: http://lkml.kernel.org/r/1338562358-28182-4-git-send-email-bp@amd64.org
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>
Link: <http://lkml.kernel.org/r/1338383402-3838-1-git-send-email-andre.przywara@amd.com>
[Boris: correct and expand commit message]
Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Diffstat (limited to 'samples/trace_events')
0 files changed, 0 insertions, 0 deletions