[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v5 02/12] xen/arm: add SVE vector length field to the domain
- To: Luca Fancellu <Luca.Fancellu@xxxxxxx>
- From: Julien Grall <julien@xxxxxxx>
- Date: Thu, 13 Apr 2023 20:53:41 +0100
- Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Wei Chen <Wei.Chen@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Wei Liu <wl@xxxxxxx>
- Delivery-date: Thu, 13 Apr 2023 19:53:51 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
Hi Luca,
On 13/04/2023 17:10, Luca Fancellu wrote:
Can we move this somewhere else to avoid adding extra padding? Also shouldn't
this be protected with #ifdef CONFIG_ARM_64 to make clear this is not supported
on Xen 32-bit?
Yes, I’ll move it and protect with CONFIG_ARM_64, is it ok for you if I move it
after:
/* Monitor options */
struct {
uint8_t privileged_call_enabled : 1;
} monitor;
Please check the padding with "pahole". If possible, it would be better to
re-use an existing one.
Ok I’ll try to use the tool
I’ve managed to use the tool, the field seems already in a good spot:
ok. Thanks for checking.
Cheers,
--
Julien Grall
|