diff options
| author | Andy Lutomirski <[email protected]> | 2016-04-02 07:01:37 -0700 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2016-04-13 11:37:45 +0200 |
| commit | fbd704374d111bed16a19261176fa30e2379c87c (patch) | |
| tree | 8b1de7476a88eae86f76dc929c37e5a129c94e6c /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | c2ee03b2a94d7ba692cf6206bbe069d5bfcc20ed (diff) | |
x86/msr: Carry on after a non-"safe" MSR access fails
This demotes an OOPS and likely panic due to a failed non-"safe" MSR
access to a WARN_ONCE() and, for RDMSR, a return value of zero.
To be clear, this type of failure should *not* happen. This patch
exists to minimize the chance of nasty undebuggable failures
happening when a CONFIG_PARAVIRT=y bug in the non-"safe" MSR helpers
gets fixed.
Tested-by: Boris Ostrovsky <[email protected]>
Signed-off-by: Andy Lutomirski <[email protected]>
Acked-by: Linus Torvalds <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Arjan van de Ven <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: KVM list <[email protected]>
Cc: Paolo Bonzini <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: xen-devel <[email protected]>
Link: http://lkml.kernel.org/r/26567b216aae70e795938f4b567eace5a0eb90ba.1459605520.git.luto@kernel.org
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions