From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Grygorii Strashko <grygorii_strashko@epam.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Michal Orzel" <michal.orzel@amd.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v3 0/4] xen/arm64: allow to make aarch32 el1 support optional
Date: Fri, 3 Oct 2025 17:07:44 +0000 [thread overview]
Message-ID: <87y0prncbk.fsf@epam.com> (raw)
In-Reply-To: <20250911082034.1326377-1-grygorii_strashko@epam.com> (Grygorii Strashko's message of "Thu, 11 Sep 2025 08:20:35 +0000")
Hi Grygorii,
Grygorii Strashko <grygorii_strashko@epam.com> writes:
> From: Grygorii Strashko <grygorii_strashko@epam.com>
>
> Hi,
>
> During review of v1 [1] of this series Julien Grall raised concern that
> "If the desire is to make 32-bit domain optional on Arm64.
> Then I think it would be better to pass the domain type when the domain is
> created (IOW add an extra flags to XEN_DOMCTL_createdomain)." for which
> I've sent patches attempting to start solving the problem [2] and try to
> probe guest kernels before creating domains. While proposed changes [2] is
> under review and hence there are definitely more work is required I'd
> appreciated if current series can be considered as it's Arm specific only
> and working (and tested) with current Xen in its current state.
I am not sure that this is a great idea. Domain creation process is
convoluted enough and your patch 3 makes it more convoluted and hard to
follow. Probably it is better to wait while [2] series will be merged
and then revisit this series.
[...]
--
WBR, Volodymyr
prev parent reply other threads:[~2025-10-03 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 8:20 [PATCH v3 0/4] xen/arm64: allow to make aarch32 el1 support optional Grygorii Strashko
2025-09-11 8:20 ` [PATCH v3 2/4] xen/arm: split is_32bit/64bit_domain() between arm64/arm32 Grygorii Strashko
2025-09-11 8:20 ` [PATCH v3 1/4] xen/arm: split set_domain_type() " Grygorii Strashko
2025-09-11 8:20 ` [PATCH v3 4/4] xen/arm64: constify is_32/64bit_domain() macro for CONFIG_ARM64_AARCH32=n Grygorii Strashko
2025-09-11 8:20 ` [PATCH v3 3/4] xen/arm64: allow to make aarch32 el1 support optional Grygorii Strashko
2025-10-03 17:07 ` Volodymyr Babchuk [this message]
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=87y0prncbk.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=grygorii_strashko@epam.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.