qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-arm@nongnu.org, alex.bennee@linaro.org,
	"Peter Maydell" <peter.maydell@linaro.org>,
	kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH 09/13] target/arm/cpu: define ARM_MAX_VQ once for aarch32 and aarch64
Date: Tue, 18 Mar 2025 15:02:00 -0700	[thread overview]
Message-ID: <52000c3d-827f-4e21-afa3-f191c6636b9d@linaro.org> (raw)
In-Reply-To: <a88f54cb-73be-4947-b3be-aa12b120f07e@linaro.org>

On 3/18/25 11:50, Philippe Mathieu-Daudé wrote:
> On 18/3/25 05:51, Pierrick Bouvier wrote:
>> This will affect zregs field for aarch32.
>> This field is used for MVE and SVE implementations. MVE implementation
>> is clipping index value to 0 or 1 for zregs[*].d[],
>> so we should not touch the rest of data in this case anyway.
> 
> We should describe why it is safe for migration.
> 
> I.e. vmstate_za depends on za_needed() -> SME, not included in 32-bit
> cpus, etc.
> 
> Should we update target/arm/machine.c in this same patch, or a
> preliminary one?
> 

vmstate_za definition and inclusion in vmstate_arm_cpu is under #ifdef 
TARGET_AARCH64. In this case (TARGET_AARCH64), ARM_MAX_VQ was already 
defined as 16, so there should not be any change.

Other values depending on ARM_MAX_VQ, for migration, are as well under 
TARGET_AARCH64 ifdefs (vmstate_zreg_hi_reg, vmstate_preg_reg, vmstate_vreg).

And for vmstate_vfp, which is present for aarch32 as well, the size of 
data under each register is specifically set to 2.
VMSTATE_UINT64_SUB_ARRAY(env.vfp.zregs[0].d, ARMCPU, 0, 2)

So even if storage has more space, it should not impact any usage of it.

Even though this change is trivial, I didn't do it blindly to "make it 
compile" and I checked the various usages of ARM_MAX_VQ and zregs, and I 
didn't see anything that seems to be a problem.

>>
>> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>> ---
>>    target/arm/cpu.h | 6 +-----
>>    1 file changed, 1 insertion(+), 5 deletions(-)
>>
>> diff --git a/target/arm/cpu.h b/target/arm/cpu.h
>> index 27a0d4550f2..00f78d64bd8 100644
>> --- a/target/arm/cpu.h
>> +++ b/target/arm/cpu.h
>> @@ -169,11 +169,7 @@ typedef struct ARMGenericTimer {
>>     * Align the data for use with TCG host vector operations.
>>     */
>>    
>> -#ifdef TARGET_AARCH64
>> -# define ARM_MAX_VQ    16
>> -#else
>> -# define ARM_MAX_VQ    1
>> -#endif
>> +#define ARM_MAX_VQ    16
>>    
>>    typedef struct ARMVectorReg {
>>        uint64_t d[2 * ARM_MAX_VQ] QEMU_ALIGNED(16);
> 


  reply	other threads:[~2025-03-18 22:02 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  4:51 [PATCH 00/13] single-binary: start make hw/arm/ common (boot.c) Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 01/13] exec/cpu-all: restrict BSWAP_NEEDED to target specific code Pierrick Bouvier
2025-03-18 21:41   ` Richard Henderson
2025-03-18 22:35     ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 02/13] exec/cpu-all: restrict compile time assert " Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 03/13] exec/target_page: runtime defintion for TARGET_PAGE_BITS_MIN Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 04/13] exec/cpu-all: allow to include specific cpu Pierrick Bouvier
2025-03-18 22:11   ` Richard Henderson
2025-03-18 22:16     ` Pierrick Bouvier
2025-03-18 22:21       ` Richard Henderson
2025-03-18 22:25         ` Pierrick Bouvier
2025-03-18 22:36           ` Richard Henderson
2025-03-18 22:58             ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 05/13] target/arm/cpu: move KVM_HAVE_MCE_INJECTION to kvm-all.c file directly Pierrick Bouvier
2025-03-18 22:19   ` Richard Henderson
2025-03-19 23:06     ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 06/13] exec/poison: KVM_HAVE_MCE_INJECTION can now be poisoned Pierrick Bouvier
2025-03-18 22:22   ` Richard Henderson
2025-03-18  4:51 ` [PATCH 07/13] target/arm/cpu: always define kvm related registers Pierrick Bouvier
2025-03-18 18:14   ` Philippe Mathieu-Daudé
2025-03-18 18:23     ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 08/13] target/arm/cpu: flags2 is always uint64_t Pierrick Bouvier
2025-03-18 22:40   ` Richard Henderson
2025-03-19 23:17     ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 09/13] target/arm/cpu: define ARM_MAX_VQ once for aarch32 and aarch64 Pierrick Bouvier
2025-03-18 18:50   ` Philippe Mathieu-Daudé
2025-03-18 22:02     ` Pierrick Bouvier [this message]
2025-03-19  7:03       ` Philippe Mathieu-Daudé
2025-03-19 23:09         ` Pierrick Bouvier
2025-03-18 22:44   ` Richard Henderson
2025-03-18  4:51 ` [PATCH 10/13] target/arm/cpu: define same set of registers " Pierrick Bouvier
2025-03-18 22:45   ` Richard Henderson
2025-03-19 23:25     ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 11/13] target/arm/cpu: remove inline stubs for aarch32 emulation Pierrick Bouvier
2025-03-18 17:42   ` Philippe Mathieu-Daudé
2025-03-18 17:50     ` Peter Maydell
2025-03-18 17:52       ` Pierrick Bouvier
2025-03-18 18:06         ` Peter Maydell
2025-03-18 18:13           ` Pierrick Bouvier
2025-03-19 23:35             ` Pierrick Bouvier
2025-03-18 18:44       ` Philippe Mathieu-Daudé
2025-03-18 17:50     ` Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 12/13] meson: add common hw files Pierrick Bouvier
2025-03-18  4:51 ` [PATCH 13/13] hw/arm/boot: make compilation unit hw common Pierrick Bouvier

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=52000c3d-827f-4e21-afa3-f191c6636b9d@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).