From: Grygorii Strashko <grygorii_strashko@epam.com>
To: "Orzel, Michal" <michal.orzel@amd.com>,
Julien Grall <julien@xen.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [XEN][PATCH 0/8] xen/arm64: make aarch32 support optional
Date: Wed, 23 Jul 2025 14:48:43 +0300 [thread overview]
Message-ID: <add27fd8-aaa2-453a-b502-fd505ec77f94@epam.com> (raw)
In-Reply-To: <e35822cc-d8a0-49c1-a4b1-2765e0e6cb6c@amd.com>
On 23.07.25 13:54, Orzel, Michal wrote:
>
>
> On 23/07/2025 10:06, Julien Grall wrote:
>>
>>
>> On 23/07/2025 08:58, Grygorii Strashko wrote:
>>> From: Grygorii Strashko <grygorii_strashko@epam.com>
>>>
>>> Hi,
>>
>> Hi Grygorii,
>>
>>> Now Arm64 AArch32 guest support is always enabled and built-in while not
>>> all Arm64 platforms supports AArch32 or this support might not be needed.
>>
>> I am not entirely sure I like the proliferation of using CONFIG_* for
>> every single feature. This makes the testing a bit more complicated.
>>
>> Can you clarify what the goal with this patch?
> AArch32 is used quite rarely in embedded systems. Also, in Armv9A it might only
> be implemented at EL0 if at all. When focusing on safety certification, AArch32
> related code in Xen leaves a gap in terms of coverage that cannot really be
> justified in words. This leaves us with two options: either support it (lots of
> additional testing, requirements and documents would be needed) or compile it out.
FYI. bloat-o-meter report for this series with CONFIG_ARM64_AARCH32=n, CONFIG_EXPERT=y
add/remove: 0/6 grow/shrink: 2/32 up/down: 276/-5672 (-5396)
Function old new delta
do_trap_guest_sync 1588 1856 +268
start_xen 2456 2464 +8
make_cpus_node 832 820 -12
arch_vcpu_create 328 312 -16
vfp_save_state 132 112 -20
vfp_restore_state 132 112 -20
is_guest_pv32_psr 20 - -20
construct_hwdom 1208 1188 -20
construct_domU 2544 2524 -20
make_hypervisor_node 2048 2016 -32
inject_undef64_exception 112 80 -32
inject_abt64_exception 164 132 -32
show_registers 260 224 -36
arm64_set_domain_type 128 88 -40
do_deprecated_hypercall 124 80 -44
construct_domain 316 272 -44
init_xen_cap_info 96 44 -52
continue_new_vcpu 188 136 -52
check_conditional_instr 192 140 -52
vsmccc_handle_call 1328 1272 -56
make_timer_node 492 436 -56
vcpu_regs_user_to_hyp 512 448 -64
vcpu_regs_hyp_to_user 512 448 -64
do_common_cpu_on 440 372 -68
cpsr_switch_mode 80 - -80
advance_pc 140 32 -108
do_trap_stage2_abort_guest 836 724 -112
arch_set_info_guest 336 184 -152
inject_undef_exception 180 20 -160
arch_do_multicall_call 632 468 -164
schedule_tail 752 576 -176
decode_thumb2 200 - -200
subarch_do_domctl 276 40 -236
inject_abt32_exception 236 - -236
do_debug_trap 256 - -256
hypercall_create_continuation 1228 848 -380
_show_registers 832 380 -452
decode_instruction 1032 476 -556
do_trap_hypercall 640 - -640
guest_walk_tables 1896 984 -912
Total: Before=670920, After=665524, chg -0.80%
add/remove: 0/0 grow/shrink: 0/0 up/down: 0/0 (0)
Data old new delta
Total: Before=448625, After=448625, chg +0.00%
add/remove: 0/0 grow/shrink: 1/0 up/down: 191/0 (191)
RO Data old new delta
xen_config_data 1345 1536 +191
Total: Before=18498, After=18689, chg +1.03%
--
Best regards,
-grygorii
next prev parent reply other threads:[~2025-07-23 11:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 7:58 [XEN][PATCH 0/8] xen/arm64: make aarch32 support optional Grygorii Strashko
2025-07-23 7:58 ` [XEN][PATCH 1/8] xen/arm: split set_domain_type() between arm64/arm32 Grygorii Strashko
2025-07-23 7:58 ` [XEN][PATCH 2/8] xen/arm: move vcpu_switch_to_aarch64_mode() in arch_vcpu_create() Grygorii Strashko
2025-07-23 9:16 ` Julien Grall
2025-07-23 10:19 ` Grygorii Strashko
2025-07-23 11:09 ` Julien Grall
2025-07-24 13:54 ` Grygorii Strashko
2025-07-23 11:12 ` Andrew Cooper
2025-07-23 7:58 ` [XEN][PATCH 3/8] xen/arm: move vcpu_switch_to_aarch64_mode() in arm64 Grygorii Strashko
2025-07-23 9:22 ` Julien Grall
2025-07-23 10:45 ` Grygorii Strashko
2025-07-23 7:58 ` [XEN][PATCH 4/8] xen/arm: split is_32bit/64bit_domain() between arm64/arm32 Grygorii Strashko
2025-07-23 8:32 ` Andrew Cooper
2025-07-23 7:58 ` [XEN][PATCH 6/8] xen/arm64: constify is_32/64bit_domain() macro for CONFIG_ARM64_AARCH32=n Grygorii Strashko
2025-07-23 8:37 ` Andrew Cooper
2025-07-23 7:58 ` [XEN][PATCH 5/8] xen/arm64: make aarch32 support optional Grygorii Strashko
2025-07-23 7:58 ` [XEN][PATCH 7/8] xen/arm: regs.h split subarch definitions between arm64/arm32 Grygorii Strashko
2025-07-23 7:58 ` [XEN][PATCH 8/8] xen/arm64: constify regs_mode_is_32bit macro for CONFIG_ARM64_AARCH32=n Grygorii Strashko
2025-07-23 8:06 ` [XEN][PATCH 0/8] xen/arm64: make aarch32 support optional Julien Grall
2025-07-23 10:54 ` Orzel, Michal
2025-07-23 11:48 ` Grygorii Strashko [this message]
2025-07-23 12:02 ` Julien Grall
2025-07-23 12:12 ` Grygorii Strashko
2025-07-24 14:24 ` Grygorii Strashko
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=add27fd8-aaa2-453a-b502-fd505ec77f94@epam.com \
--to=grygorii_strashko@epam.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.