lkml.org 
[lkml]   [2022]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [RFC 07/10] platform/x86/intel/ifs: Create kthreads for online cpus for scan test
Date
>> These are software(driver) defined error codes. Rest of the error codes are supplied by
>> the hardware. Software defined error codes were kept at the other end to provide ample space
>> in case (future) hardware decides to provide extend error codes.
>
> Why put them in the same number space? Separate software results from
> the raw hardware results and have a separate mechanism to convey each.

We wanted to include in the "details" file, which is otherwise a direct copy of
the SCAN_STATUS MSR. Making sure the software error codes didn't overlap
with any h/w generated codes seemed like a good idea.

But maybe we should have done this with additional string values in the status
file:

Current:

pass
untested
fail

Add a couple of new options for the s/w cases:

sw_timeout
sw_retries_exceeded

-Tony

\
 
 \ /
  Last update: 2022-03-07 18:49    [W:0.080 / U:0.580 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site