[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xen FuSa Meeting Nov 17 minutes


  • To: <fusa-sig@xxxxxxxxxxxxxxxxxxxx>
  • From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>
  • Date: Tue, 17 Nov 2020 10:30:02 -0800
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 149.199.62.198) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=xilinx.com; dmarc=bestguesspass action=none header.from=xilinx.com; dkim=none (message not signed); arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HdDnWpFX/rDSY7YIWY0qXd4ghKCsKq+U/eZDZgOHyXY=; b=MibMiji/xU7pEWJ3R63kqF8VCdzmt0uWiAqa5wNIIuP2zj+46Bq0RldPMdj27QSoYMiah1og6eyLn0eovpDlDYR3xWk1hFF6u4Evplh9Pyg2L5Bp5tAZSlBgkTI4FPMu7mvK+JJ56aCwi2M+TH3NiCSIEqSmYpM7IpElyFFeEGkVdELARbBgYxrzpBT/F/wvdHyY4aOamVSUArplvkPPTVUS152wr/GnAwgYnr0uXdSZdEWEBj2VH4flBXhajmDhM0h4IW/ZxRYc9+DDth/wXxGnnMsj6+UnHeK8+kGCcqZSq6/rlVDT0Jf8fEQQwAN2yE0+V7oCtUjP3Lj8rzkxwQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lh3K3mtfZkoPm5U1uEQroOvWMJrR2SQI39sKpV2qPTOPWRCN04J5bRKtb/dq5btK7u4U8Fh4l3oKDHyFgSAcvyMYRnqQXpq5zGi5l8W4hPfD+E8OSkWlSrIVXzNRA6sy+KDIso6zPqWiQfy+25OeruKsCEbuU60zLSGAvMY6kqx4UTq5+pMpV+sCmhxH8JnDKmoMIwpSpleo0Iec8mobwe48deSGtNKhrikPfOuidUEZ8BDASDfQe/X+0zGRFy71qYRduVVzs2PsAQYjuav1oUfcOzf653REuO2ADh3PRAkBMz68GHCHYUdJWUE792/mhqHBtCMJ5g7y+OLtJNNDmg==
  • Cc: <stefanos@xxxxxxxxxx>
  • Delivery-date: Tue, 17 Nov 2020 18:30:08 +0000
  • List-id: This is a discussion list for members of the Xen Project FuSa SIG <fusa-sig.lists.xenproject.org>

Hi all,

These are the minutes from today's meeting (Tue November 17).

Cheers,

Stefano

---

#  MISRA Compliance 2020

David Ward gave a clear presentation on MISRA Compliance 2020. It
supersedes previous compliance and deviation mechanisms and provides a
rigorous framework to handle compliance, re-categorization (i.e.
Advisory->Required) and deviations. It includes a set of permits, which
are common deviation cases.

Input:
- MISRAC
- guideline enforcement plan (including the tools to use)
    - used to be called compliance matrix
    - for each guideline what method we use to demonstrate we comply
- guideline re-categorization plan
    - some required can me made mandatory
    - some advisory can be made mandatory, required or disappear
    - cannot remove a required guideline
- permits
    - common deviation cases

Output:
- guideline compliance summary
- approved deviations
- permits

ACTION(David): send slides to the list


# ARMClang

ACTION(Bertrand): send license to Artem
ACTION(Bertrand): invite compilers guys to a Xen FuSa meeting


# MISRAC Checkers

We briefly touched on tools to check for MISRAC.  SonarCloud has very
limited MISRAC support. cppcheck claims to have 143 rules covered and
seems promising. More investigation is required.

Stefano showed a diagram on how to potentially integrate MISRAC checkers
in Xen Project's processes using the gitlab CI-loop, so that they can be
automatically called on patch series submissions, locally by
contributors, and automatically by the CI-loop.

ACTION(Artem,Francesco): continue investigation on MISRAC checkers that
could be called automatically from the CI-loop and configured with a
provided list of deviations.

Bertrand is going to provide an update on Doxygen during the next
meeting.



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.