Discuss: --log-level option and clarifying log levels

[ivanhu]

Hi Colin,

We also have the warnings on fwts, should we add it as well?

like,
warning: don't affect the machine and functions, the design wasn't 
correct or following the specifications and rules.

Cheers,
Ivan

On 2015年12月10日 18:24, Colin Ian King wrote:
> Hi there,
>
> I'm thinking of adding a --log-level option to fwts.
>
> fwts --log-level=[critical|high|medium|low|info]
>
> It will basically only print out and account for fwts errors of the
> given level or higher.  E.g.
>
> fwts --log-level=high will just account for errors that are high or
> critical.
>
> The fwts team are also thinking of clarifying the meanings of these
> levels and fixing up all the error messages to match the definition.
>
> So let's try and start to define this properly. I am proposing:
>
> critical:  errors that can stop a machine from working, or can make it
> behave in a way detrimental to the hardware.
>
> high:  errors that will make the machine perform incorrectly or
> sub-optimally
>
> medium:  issues that would be useful to fix as they cause kernel message
> but the kernel can fix these up or work around the error and the machine
> will function fine.
>
> low:  miscellaneous small issues but don't affect the machine, the user
> won't notice any kernel warnings and fixing this won't make any difference.
>
> info: not really a error, just some useful help information about a very
> minor issue that really is worth noting to give some feedback about why
> the kernel may print a message, e.g. "PnPBIOS Disabled by ACPI PNP".
>
> Feel free to comment on these definitions so we can hone these into
> something workable.
>
> Colin
>