Xen FuSA SIG Feb 2 meeting minutes

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>]

Hi all,

Today during the Xen FuSa SIG meeting we went through the first few
items of the MISRAC rules list, adding comments on whether they apply
for Xen and how to automatically check for compliance:

https://cryptpad.fr/sheet/#/2/sheet/edit/29hTgZp-z9LffFhe5fs9rOQJ/

Please note that the previous link to the sheet that I sent didn't work.
Please use this one.


For your convenience I copy/pasted the rules we discussed here together
with our notes:

* Dir 1.1  Any implementation-defined behaviour on which the output of the 
program depends shall be documented and understood
Applies to Xen: Yes
Check: gcc strict ansi ??? what about preprocessor macros?

* Dir 2.1  All source files shall compile without any compilation errors
Applies to Xen: Yes
Check: gcc -Werror -Wall -Wextra

* Dir 3.1  All code shall be traceable to documented requirements
Applies to Xen: Yes
Check: Doorstop + manual review
To be done at a later stage

* Dir 4.1  Run-time failures shall be minimized
Applies to Xen: Yes
Check: gcc option to check for return values (-Wall); BUG_ON at init is OK; no 
BUG_ON at runtime (e.g. reference a __init variable); document it all



We also discussed the high level requirement example by Bertrand. He
took an action to send out an update based on the feedback.

https://gitlab.com/xen-project/fusa/fusa-docs/-/blob/master/high-level/hlrq-hypercalls.rst


Cheers,

Stefano