From: "Orzel, Michal" <michal.orzel@amd.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.com>,
<xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH v1 3/3] xen: introduce CONFIG_HAS_DOMAIN_TYPE
Date: Tue, 21 Apr 2026 13:55:18 +0200 [thread overview]
Message-ID: <1eeb93a1-bb57-4ac8-a280-2b78b045fc2f@amd.com> (raw)
In-Reply-To: <aa51f23b-0e2f-4666-93ee-038430f661ab@gmail.com>
On 21/04/2026 13:06, Oleksii Kurochko wrote:
>
>
> On 4/20/26 10:03 AM, Orzel, Michal wrote:
>>
>>
>> On 16/04/2026 16:21, Oleksii Kurochko wrote:
>>> As domain type is part of common code now there is no any reason
>>> to have architecture-specific set_domain_type() functions so
>>> it is dropped.
>>>
>>> The CONFIG_ARM_64 guard in xen/arch/arm/domain_build.c is intentionally
>>> left unchanged: it is ARM-specific code, and ARM_64 selects
>>> HAS_DOMAIN_TYPE, so the semantics are identical.
>>>
>>> x86 with CONFIG_64BIT=y shouldn't use is_{32,64}bit_domain() as
>>> x86 doesn't have support of CONFIG_HAS_DOMAIN_TYPE. For x86_32
>>> it is fine to follow generic is_{32,64}_bit_domain() implementations.
>> I thought x86_32 Xen no longer builds. This means the fallback is only for arm32.
>
> Will you be okay with
> Since x86_32 Xen no longer builds, the fallback is currently only
> relevant for arm32.
Yes. I would.
~Michal
next prev parent reply other threads:[~2026-04-21 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 14:20 [PATCH v1 0/3] dom0less: various updates Oleksii Kurochko
2026-04-16 14:20 ` [PATCH v1 1/3] xen/dom0less: introduce free_phandle in struct kernel_info Oleksii Kurochko
2026-04-20 7:26 ` Orzel, Michal
2026-04-21 10:47 ` Oleksii Kurochko
2026-04-16 14:20 ` [PATCH v1 2/3] xen/dom0less: pass kernel_info struct instead of fdt to make_cpus_node() Oleksii Kurochko
2026-04-20 7:29 ` Orzel, Michal
2026-04-21 10:48 ` Oleksii Kurochko
2026-04-16 14:21 ` [PATCH v1 3/3] xen: introduce CONFIG_HAS_DOMAIN_TYPE Oleksii Kurochko
2026-04-20 8:03 ` Orzel, Michal
2026-04-21 11:06 ` Oleksii Kurochko
2026-04-21 11:55 ` Orzel, Michal [this message]
2026-04-20 8:22 ` Jan Beulich
2026-04-21 11:53 ` Oleksii Kurochko
2026-04-21 13:12 ` Jan Beulich
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=1eeb93a1-bb57-4ac8-a280-2b78b045fc2f@amd.com \
--to=michal.orzel@amd.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=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.