All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v1 4/9] asm-generic: move Arm's static-memory.h to asm-generic
Date: Mon, 3 Feb 2025 16:45:57 +0100	[thread overview]
Message-ID: <3a0fbade-c75a-454c-875b-4d8acecf5939@gmail.com> (raw)
In-Reply-To: <58f861e2-866d-4c11-9bdb-b4b6c84825af@suse.com>

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]


On 1/27/25 12:19 PM, Jan Beulich wrote:
> On 08.01.2025 12:13, Oleksii Kurochko wrote:
>> Except moving Arm's static-memory.h to asm-generic #ifdef header guard
>> is updated: s/__ASM_STATIC_MEMORY_H_/__ASM_GENERIC_STATIC_MEMORY_H__.
>>
>> Update arm/include/asm/Makefile to use asm-generic version of
>> static-memory.h for Arm.
>>
>> Signed-off-by: Oleksii Kurochko<oleksii.kurochko@gmail.com>
> Here as well as in patch 5 the "why" is again missing. Moving is fine, as
> long as it's clear that this will actually be used by another arch (e.g.
> RISC-V). Whether you have such (immediate or at least near term) plans is
> unclear though, as both features look like relatively advanced ones, and
> hence more basic functionality may want to appear first in RISC-V.

The reason is that suggested generic dom0less solution is using allocate_static_memory() and
assign_static_memory_11() so I decided that it would be better to have stubs for them in
asm-generic header that wrapping by the code by "#ifdef CONFIG_STATIC_MEMORY" the places where
it is used.
But considering the status of RISC-V's Xen downstream and I still don't have cases where CONFIG_STATIC_MEMORY
is used for RISC-V, probably, it would be better just to use wrapping in generic code instead of
stubs.

~ Oleksii

[-- Attachment #2: Type: text/html, Size: 1885 bytes --]

  reply	other threads:[~2025-02-03 15:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 11:13 [PATCH for 4.21 v1 0/9] Move parts of Arm's Dom0less to common code Oleksii Kurochko
2025-01-08 11:13 ` [PATCH v1 1/9] xen/common: dom0less: make some parts of Arm's CONFIG_DOM0LESS common Oleksii Kurochko
2025-01-27 11:12   ` Jan Beulich
2025-02-03 15:18     ` Oleksii Kurochko
2025-01-08 11:13 ` [PATCH v1 2/9] asm-generic: move parts of Arm's asm/kernel.h to asm-generic Oleksii Kurochko
2025-01-27 11:15   ` Jan Beulich
2025-02-03 15:34     ` Oleksii Kurochko
2025-02-03 16:33       ` Jan Beulich
2025-01-08 11:13 ` [PATCH v1 3/9] arm/static-shmem.h: drop inclusion of asm/setup.h Oleksii Kurochko
2025-01-08 11:13 ` [PATCH v1 4/9] asm-generic: move Arm's static-memory.h to asm-generic Oleksii Kurochko
2025-01-27 11:19   ` Jan Beulich
2025-02-03 15:45     ` Oleksii Kurochko [this message]
2025-01-08 11:13 ` [PATCH v1 5/9] asm-generic: move Arm's static-shmem.h " Oleksii Kurochko
2025-01-08 11:13 ` [PATCH v1 6/9] asm-generic: move some parts of Arm's domain_build.h to asm-generic header Oleksii Kurochko
2025-01-27 11:23   ` Jan Beulich
2025-02-03 15:50     ` Oleksii Kurochko
2025-02-03 16:38       ` Jan Beulich
2025-01-08 11:13 ` [PATCH v1 7/9] xen/common: dom0less: introduce common kernel.c Oleksii Kurochko
2025-01-08 11:13 ` [PATCH v1 8/9] xen/common: dom0less: introduce common domain-build.c Oleksii Kurochko
2025-01-08 11:13 ` [PATCH v1 9/9] xen/common: dom0less: introduce common dom0less-build.c Oleksii Kurochko

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=3a0fbade-c75a-454c-875b-4d8acecf5939@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.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.