From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
"Nicola Vetrini" <nicola.vetrini@bugseng.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Michal Orzel" <michal.orzel@amd.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Dario Faggioli" <dfaggioli@suse.com>
Subject: [XEN PATCH 0/7] address violations of MISRA C:2012 Rule 2.1
Date: Mon, 11 Dec 2023 11:30:21 +0100 [thread overview]
Message-ID: <cover.1702283415.git.nicola.vetrini@bugseng.com> (raw)
MISRA C:2012 Rule 2.1 states: "A project shall not contain unreachable code".
As such, this series eliminates various instances of unreachable code found in
Xen, by providing equivalent compliant constructs.
This series is loosely based on my earlier series [1], but the overall approach
has changed since; for instance, declarations without initialization are now
ignored, as detailed in docs/misra/deviations.rst.
[1] https://lore.kernel.org/xen-devel/cover.1690985045.git.nicola.vetrini@bugseng.com/
Nicola Vetrini (7):
xen/shutdown: address MISRA C:2012 Rule 2.1
x86/mm: address MISRA C:2012 Rule 2.1
xen/arm: address MISRA C:2012 Rule 2.1
xen/sched: address MISRA C:2012 Rule 2.1
xen/arm: traps: add ASSERT_UNREACHABLE() where needed
x86/platform: removed break to address MISRA C:2012 Rule 2.1
x86/xstate: move BUILD_BUG_ON to address MISRA C:2012 Rule 2.1
xen/arch/arm/mm.c | 2 +-
xen/arch/arm/traps.c | 6 +++---
xen/arch/arm/vgic-v3-its.c | 10 +++++-----
xen/arch/x86/mm.c | 6 +++---
xen/arch/x86/platform_hypercall.c | 1 -
xen/arch/x86/xstate.c | 3 ++-
xen/common/sched/core.c | 1 -
xen/common/shutdown.c | 11 ++---------
xen/include/xen/shutdown.h | 2 +-
9 files changed, 17 insertions(+), 25 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-11 10:30 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 10:30 Nicola Vetrini [this message]
2023-12-11 10:30 ` [XEN PATCH 1/7] xen/shutdown: address MISRA C:2012 Rule 2.1 Nicola Vetrini
2023-12-12 1:39 ` Stefano Stabellini
2023-12-12 9:45 ` Jan Beulich
2023-12-12 9:53 ` Nicola Vetrini
2023-12-12 10:30 ` Jan Beulich
2023-12-11 10:30 ` [XEN PATCH 2/7] x86/mm: " Nicola Vetrini
2023-12-12 1:42 ` Stefano Stabellini
2023-12-12 9:12 ` Nicola Vetrini
2023-12-12 9:53 ` Jan Beulich
2023-12-13 14:44 ` Nicola Vetrini
2023-12-14 7:57 ` Jan Beulich
2023-12-14 8:52 ` Nicola Vetrini
2023-12-11 10:30 ` [XEN PATCH 3/7] xen/arm: " Nicola Vetrini
2023-12-11 12:29 ` Julien Grall
2023-12-11 13:06 ` Michal Orzel
2023-12-11 14:14 ` Julien Grall
2023-12-11 14:52 ` Nicola Vetrini
2023-12-11 10:30 ` [XEN PATCH 4/7] xen/sched: " Nicola Vetrini
2023-12-11 13:30 ` George Dunlap
2023-12-12 1:43 ` Stefano Stabellini
2023-12-11 10:30 ` [XEN PATCH 5/7] xen/arm: traps: add ASSERT_UNREACHABLE() where needed Nicola Vetrini
2023-12-11 12:32 ` Julien Grall
2023-12-11 14:54 ` Nicola Vetrini
2023-12-11 15:59 ` Julien Grall
2023-12-11 16:05 ` Julien Grall
2023-12-11 17:36 ` Nicola Vetrini
2023-12-12 1:36 ` Stefano Stabellini
2023-12-12 9:23 ` Julien Grall
2023-12-12 15:49 ` Julien Grall
2023-12-13 14:02 ` Nicola Vetrini
2023-12-14 9:42 ` Julien Grall
2023-12-14 22:32 ` Stefano Stabellini
2023-12-15 11:03 ` Nicola Vetrini
2023-12-15 14:08 ` Nicola Vetrini
2023-12-15 18:18 ` Julien Grall
2023-12-15 21:02 ` Stefano Stabellini
2023-12-11 10:30 ` [XEN PATCH 6/7] x86/platform: removed break to address MISRA C:2012 Rule 2.1 Nicola Vetrini
2023-12-12 1:44 ` Stefano Stabellini
2023-12-12 10:13 ` Jan Beulich
2023-12-12 22:38 ` Stefano Stabellini
2023-12-13 10:43 ` Nicola Vetrini
2023-12-11 10:30 ` [XEN PATCH 7/7] x86/xstate: move BUILD_BUG_ON " Nicola Vetrini
2023-12-12 1:46 ` Stefano Stabellini
2023-12-12 10:04 ` Jan Beulich
2023-12-12 10:07 ` Jan Beulich
2023-12-12 13:38 ` Nicola Vetrini
2023-12-12 14:01 ` Jan Beulich
2023-12-12 14:05 ` Nicola Vetrini
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.1702283415.git.nicola.vetrini@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=dfaggioli@suse.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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.