lkml.org 
[lkml]   [2015]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v4] x86: mce: kexec: switch MCE handler for kexec/kdump
Date
> - fixed AR and UC order in enum severity_level because UC is severer than AR
> by definition. Current code is not affected by this wrong order by chance.

AR and AO are both UC errors - that happen also to be recoverable. Are you really sure
about this re-order not affecting existing code? You might well be right, but as every one
else has pointed out mce_severity() is full of odd subtleties that catch people out.

Is the "UC" entry at the end of the severities[] table just a catch-all for things that made it
past all the other entries? Does it ever really get used?

What was the test case that made you promote UC above AR?

This absolutely should not be buried in the middle of your other patch - it needs to
be separate with a much more than two lines of commit description.

-Tony


\
 
 \ /
  Last update: 2015-03-05 00:21    [W:0.118 / U:0.788 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site