diff options
author | Borislav Petkov <[email protected]> | 2011-04-18 16:00:21 +0200 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2011-04-19 19:14:13 +0200 |
commit | 7b70bd3441437b7bc04fc9d321e17c8ed0e8f958 (patch) | |
tree | 4fc610ccefebf7688adc9b71029fbd36390a6c35 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | f0e615c3cb72b42191b558c130409335812621d8 (diff) |
x86, MCE: Do not taint when handling correctable errors
Correctable errors are considered something rather normal on
modern hardware these days. Even more importantly, correctable
errors mean exactly that - they've been corrected by the
hardware - and there's no need to taint the kernel since
execution hasn't been compromised so far.
Also, drop tainting in the thermal throttling code for a similar
reason: crossing a thermal threshold does not mean corruption.
Signed-off-by: Borislav Petkov <[email protected]>
Acked-by: Tony Luck <[email protected]>
Acked-by: Nagananda Chumbalkar <[email protected]>
Cc: Prarit Bhargava <[email protected]>
Cc: Russ Anderson <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Andrew Morton <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions