From: Oleksii <oleksii.kurochko@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: Shawn Anastasio <sanastasio@raptorengineering.com>,
George Dunlap <George.Dunlap@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>
Subject: Re: [PATCH 1/3] xen/riscv: Drop legacy __ro_after_init definition
Date: Mon, 24 Jun 2024 14:50:41 +0200 [thread overview]
Message-ID: <2bd871f45ec63f29ee6c7637799c73bab1ca5b3c.camel@gmail.com> (raw)
In-Reply-To: <20240621201928.319293-2-andrew.cooper3@citrix.com>
On Fri, 2024-06-21 at 21:19 +0100, Andrew Cooper wrote:
> Hide the legacy __ro_after_init definition in xen/cache.h for RISC-V,
> to avoid
> its use creeping in. Only mm.c needs adjusting as a consequence
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>
~ Oleksii
> ---
> CC: Shawn Anastasio <sanastasio@raptorengineering.com>
> CC: Oleksii Kurochko <oleksii.kurochko@gmail.com>
> CC: George Dunlap <George.Dunlap@citrix.com>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> CC: Julien Grall <julien@xen.org>
>
> https://gitlab.com/xen-project/people/andyhhp/xen/-/pipelines/1342686294
> ---
> xen/arch/riscv/mm.c | 2 +-
> xen/include/xen/cache.h | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/xen/arch/riscv/mm.c b/xen/arch/riscv/mm.c
> index 053f043a3d2a..3ebaf6da01cc 100644
> --- a/xen/arch/riscv/mm.c
> +++ b/xen/arch/riscv/mm.c
> @@ -1,11 +1,11 @@
> /* SPDX-License-Identifier: GPL-2.0-only */
>
> -#include <xen/cache.h>
> #include <xen/compiler.h>
> #include <xen/init.h>
> #include <xen/kernel.h>
> #include <xen/macros.h>
> #include <xen/pfn.h>
> +#include <xen/sections.h>
>
> #include <asm/early_printk.h>
> #include <asm/csr.h>
> diff --git a/xen/include/xen/cache.h b/xen/include/xen/cache.h
> index 55456823c543..82a3ba38e3e7 100644
> --- a/xen/include/xen/cache.h
> +++ b/xen/include/xen/cache.h
> @@ -15,7 +15,9 @@
> #define __cacheline_aligned
> __attribute__((__aligned__(SMP_CACHE_BYTES)))
> #endif
>
> +#if defined(CONFIG_ARM) || defined(CONFIG_X86) ||
> defined(CONFIG_PPC64)
> /* TODO: Phase out the use of this via cache.h */
> #define __ro_after_init __section(".data.ro_after_init")
> +#endif
>
> #endif /* __LINUX_CACHE_H */
next prev parent reply other threads:[~2024-06-24 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 20:19 [PATCH for-4.19? 0/3] xen: build adjustments for __read_mostly/__ro_after_init Andrew Cooper
2024-06-21 20:19 ` [PATCH 1/3] xen/riscv: Drop legacy __ro_after_init definition Andrew Cooper
2024-06-24 8:02 ` Oleksii
2024-06-24 8:04 ` Jan Beulich
2024-06-24 12:51 ` Oleksii
2024-06-24 12:50 ` Oleksii [this message]
2024-06-21 20:19 ` [PATCH 2/3] xen/ppc: Adjust ppc64_defconfig Andrew Cooper
2024-09-05 21:54 ` [ping] " Andrew Cooper
2024-09-06 6:01 ` Jan Beulich
2024-06-21 20:19 ` [PATCH 3/3] xen/ppc: Avoid using the legacy __read_mostly/__ro_after_init definitions Andrew Cooper
2024-06-24 8:01 ` Jan Beulich
2024-06-24 8:04 ` Oleksii
2024-06-24 7:58 ` [PATCH for-4.19? 0/3] xen: build adjustments for __read_mostly/__ro_after_init Oleksii
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=2bd871f45ec63f29ee6c7637799c73bab1ca5b3c.camel@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien@xen.org \
--cc=sanastasio@raptorengineering.com \
--cc=sstabellini@kernel.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.