From: Julien Grall <julien@xen.org>
To: Nicola Vetrini <nicola.vetrini@bugseng.com>,
xen-devel@lists.xenproject.org
Cc: michal.orzel@amd.com, xenia.ragiadakou@amd.com,
ayan.kumar.halder@amd.com, consulting@bugseng.com,
Stefano Stabellini <sstabellini@kernel.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [XEN PATCH v2 1/3] xen/arch/arm: fix violations of MISRA C:2012 Rule 3.1
Date: Mon, 19 Jun 2023 11:01:24 +0100 [thread overview]
Message-ID: <51501199-80e6-e33f-e70a-7a36d26c1894@xen.org> (raw)
In-Reply-To: <e2b7f377d1467833d9ae2cd897c962561e54fb02.1687167502.git.nicola.vetrini@bugseng.com>
Hi,
On 19/06/2023 10:56, Nicola Vetrini wrote:
> In the files `xen/arch/arm/include/asm/arm(32|64)/flushtlb.h' there are a
> few occurrences of nested '//' character sequences inside C-style comment
> blocks, which violate Rule 3.1. The patch aims to resolve those by removing
> the nested comments.
As I wrote in
https://lore.kernel.org/xen-devel/f3fc1848-68ca-37a1-add2-e100b4773190@xen.org/,
I am against replacing '//' with nothing. I have proposed to use ';'
because this is also a valid way to comment in assembly.
>
> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com
There is a missing '>' at the end of the list.
> ---
> Changes:
> - Resending the patch with the right maintainers in CC.
> Changes in V2:
> - Split the patch into a series and reworked the fix.
> - Apply the fix to the arm32 `flushtlb.h' file, for consistency
> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
> ---
> xen/arch/arm/include/asm/arm32/flushtlb.h | 8 ++++----
> xen/arch/arm/include/asm/arm64/flushtlb.h | 8 ++++----
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/xen/arch/arm/include/asm/arm32/flushtlb.h b/xen/arch/arm/include/asm/arm32/flushtlb.h
> index 22ee3b317b..bcbeac590b 100644
> --- a/xen/arch/arm/include/asm/arm32/flushtlb.h
> +++ b/xen/arch/arm/include/asm/arm32/flushtlb.h
> @@ -4,10 +4,10 @@
> /*
> * Every invalidation operation use the following patterns:
> *
> - * DSB ISHST // Ensure prior page-tables updates have completed
> - * TLBI... // Invalidate the TLB
> - * DSB ISH // Ensure the TLB invalidation has completed
> - * ISB // See explanation below
> + * DSB ISHST Ensure prior page-tables updates have completed
> + * TLBI... Invalidate the TLB
> + * DSB ISH Ensure the TLB invalidation has completed
> + * ISB See explanation below
> *
> * For Xen page-tables the ISB will discard any instructions fetched
> * from the old mappings.
> diff --git a/xen/arch/arm/include/asm/arm64/flushtlb.h b/xen/arch/arm/include/asm/arm64/flushtlb.h
> index 56c6fc763b..6066a2d703 100644
> --- a/xen/arch/arm/include/asm/arm64/flushtlb.h
> +++ b/xen/arch/arm/include/asm/arm64/flushtlb.h
> @@ -4,10 +4,10 @@
> /*
> * Every invalidation operation use the following patterns:
> *
> - * DSB ISHST // Ensure prior page-tables updates have completed
> - * TLBI... // Invalidate the TLB
> - * DSB ISH // Ensure the TLB invalidation has completed
> - * ISB // See explanation below
> + * DSB ISHST Ensure prior page-tables updates have completed
> + * TLBI... Invalidate the TLB
> + * DSB ISH Ensure the TLB invalidation has completed
> + * ISB See explanation below
> *
> * ARM64_WORKAROUND_REPEAT_TLBI:
> * Modification of the translation table for a virtual address might lead to
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2023-06-19 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:56 [XEN PATCH v2 0/3] fix violations of MISRA C:2012 Rule 3.1 Nicola Vetrini
2023-06-19 9:56 ` [XEN PATCH v2 1/3] xen/arch/arm: " Nicola Vetrini
2023-06-19 10:01 ` Julien Grall [this message]
2023-06-19 10:25 ` Jan Beulich
2023-06-19 10:29 ` Julien Grall
2023-06-20 13:56 ` Nicola Vetrini
2023-06-19 9:56 ` [XEN PATCH v2 2/3] xen/drivers/passthrough/arm/smmu-v3.c: " Nicola Vetrini
2023-06-19 10:10 ` Julien Grall
2023-06-20 8:06 ` Nicola Vetrini
2023-06-19 9:56 ` [XEN PATCH v2 3/3] xen: " Nicola Vetrini
2023-06-19 10:29 ` Jan Beulich
2023-06-20 8:00 ` 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=51501199-80e6-e33f-e70a-7a36d26c1894@xen.org \
--to=julien@xen.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.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.