All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.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 1/9] xen/common: dom0less: make some parts of Arm's CONFIG_DOM0LESS common
Date: Mon, 27 Jan 2025 12:12:01 +0100	[thread overview]
Message-ID: <f8d4a1d4-a332-4dad-ba6e-5a127ae2187e@suse.com> (raw)
In-Reply-To: <396a60496844c8a86667f4ee57c5bedc9899f5ad.1736334615.git.oleksii.kurochko@gmail.com>

On 08.01.2025 12:13, Oleksii Kurochko wrote:
> Unify the API for creating DomUs and checking for Dom0less mode across
> architectures, including Arm and RISC-V, with potential applicability
> for PPC.

That is you mean to re-use it for RISC-V?

> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -12,6 +12,15 @@ config CORE_PARKING
>  	bool
>  	depends on NR_CPUS > 1
>  
> +config DOM0LESS_BOOT
> +	bool "Dom0less boot support" if EXPERT
> +	depends on ARM
> +	default ARM

This then would better be converted to "depends on HAVE_DOM0LESS", which
for now only Arm would select. With a dependency on XYZ the default also
doesn't need to name XYZ again, i.e. can simply be "default y".

Jan


  reply	other threads:[~2025-01-27 11:12 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 [this message]
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
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=f8d4a1d4-a332-4dad-ba6e-5a127ae2187e@suse.com \
    --to=jbeulich@suse.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=oleksii.kurochko@gmail.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.