Xen FuSa Nov 3 meeting minutes

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>]

Hi all,

These are the minutes of today's FuSa meeting.  Look for "ACTION" in the
test to find the ACTION items.

Cheers,

Stefano



# Build Xen with ARMClang

Bertrand: ARM will internally build Xen with ARMClang to validate
ARMClang against Xen. It is going to start in the next couple of months.

Artem: I have opened a bunch of issues against ARMClang. What is the
status?

Bertrand: will check

ACTION(Bertrand): ARM to let us know when issues are going to be fixed
and in which version of the compiler.

ACTION(Artem): send the ARMClang series for Xen again rebased on staging


# Resiltech presentation on MISRAC

First identify set of rules we have to comply to MISRAC. A subset of
MISRAC, but which one?  Some rules are mandatory, some others are
advisory?

Who is responsible for deciding which rules are mandatory (R1)? It is
important to have the safety experts involved.

Once we identify the R1 rules, let's use static analysis to check for
violations. For instance SonarCloud.

We need to device who is responsible for fixing the violations, and what
happens when developers say that the solution is worse than the original
code.  There is a need for a final pass by a safety expert after the
developer's analysis. In case the safety expert team identifies that the
justification cannot be accepted the code has to be fixed.


We need a tool able to process justifications for MISRAC violations
inline with the code. It is important to maintain MISRAC violation
justifications in sync with the code. Is there a tool that can do that
today?

If the tool doesn't support it, we could add scripting to it, so that we
could extract the justifications from the comments and populate the
tool's database ourselves.


ACTION(Artem): work with Sonar and see how it handles justifications
ACTION(Francesco): do an analysis on the tools and justification handling


ACTION(Stefano): MISRAC justifiaction as incode comments, is it viable
                 from a community perspective? Start the discussion.
ACTION(Stefano): Diagram to describe the new contributor process
                 workflow


MISRAC document to provide a framework to manage deviations
https://www.misra.org.uk/forum/viewtopic.php?f=241&t=1842
ACTION(David Ward): do a presentation on the topic during the next
                    FuSa meeting.