From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com,
Nicola Vetrini <nicola.vetrini@bugseng.com>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Dario Faggioli <dfaggioli@suse.com>,
Meng Xu <mengxu@cis.upenn.edu>, Juergen Gross <jgross@suse.com>,
George Dunlap <gwd@xenproject.org>,
Doug Goldstein <cardoe@cardoe.com>
Subject: [XEN PATCH 0/3] Move Xen ECLAIR configuration to analyze.yaml
Date: Fri, 14 Feb 2025 21:45:20 +0100 [thread overview]
Message-ID: <cover.1739564781.git.nicola.vetrini@bugseng.com> (raw)
The initial configuration for the ECLAIR MISRA C analysis integration into Xen
consisted of two fixed configuration files (one for arm64 and one for x86_64).
This approach shows its downsides as configuration options may change over time.
To address this issues, the configuration can be derived from the architecture's
defconfig and overridden in analyze.yaml via EXTRA_XEN_CONFIG. While doing this,
some inconsistencies that were overlooked in the hand-crafted configuration
files have been resolved following the advice of Stefano Stabellini and
Michal Orzel.
A few regressions on clean guidelines result from such configuration changes,
therefore both patches are prerequisite to the last one to keep avoid pipeline
failures.
Nicola Vetrini (3):
xen/arm: platform: address violation of MISRA C Rule 7.2
xen/sched: address violation of MISRA C Rule 8.2
automation: Update ECLAIR analysis configuration
automation/eclair_analysis/prepare.sh | 8 +-
automation/eclair_analysis/xen_arm_config | 141 --------------------
automation/eclair_analysis/xen_x86_config | 143 ---------------------
automation/gitlab-ci/analyze.yaml | 68 ++++++++++
xen/arch/arm/platforms/brcm-raspberry-pi.c | 6 +-
xen/common/sched/rt.c | 2 +-
6 files changed, 77 insertions(+), 291 deletions(-)
delete mode 100644 automation/eclair_analysis/xen_arm_config
delete mode 100644 automation/eclair_analysis/xen_x86_config
--
2.43.0
next reply other threads:[~2025-02-14 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 20:45 Nicola Vetrini [this message]
2025-02-14 20:45 ` [XEN PATCH 1/3] xen/arm: platform: address violation of MISRA C Rule 7.2 Nicola Vetrini
2025-02-14 23:04 ` Stefano Stabellini
2025-02-14 20:45 ` [XEN PATCH 2/3] xen/sched: address violation of MISRA C Rule 8.2 Nicola Vetrini
2025-02-14 23:04 ` Stefano Stabellini
2025-02-17 7:54 ` Jan Beulich
2025-02-17 8:31 ` Nicola Vetrini
2025-02-17 8:48 ` Jürgen Groß
2025-02-14 20:45 ` [XEN PATCH 3/3] automation: Update ECLAIR analysis configuration Nicola Vetrini
2025-02-14 23:04 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1739564781.git.nicola.vetrini@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=dfaggioli@suse.com \
--cc=gwd@xenproject.org \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=mengxu@cis.upenn.edu \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.