diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2024-10-31 16:52:27 +0800 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-10-31 18:28:33 +0100 |
| commit | b888c7807049cc044d10d70139cb945202fb7cd2 (patch) | |
| tree | b82b69ad32c8b6a2057a835f5fb67fb9385a5365 /module-common.c | |
| parent | 33098002a838a0450f243f5e17463aca700e923d (diff) | |
| download | qemu-b888c7807049cc044d10d70139cb945202fb7cd2.zip qemu-b888c7807049cc044d10d70139cb945202fb7cd2.tar.gz qemu-b888c7807049cc044d10d70139cb945202fb7cd2.tar.bz2 | |
target/i386: do not rely on ExtSaveArea for accelerator-supported XCR0 bits
Right now, QEMU is using the "feature" and "bits" fields of ExtSaveArea
to query the accelerator for the support status of extended save areas.
This is a problem for AVX10, which attaches two feature bits (AVX512F
and AVX10) to the same extended save states.
To keep the AVX10 hacks to the minimum, limit usage of esa->features
and esa->bits. Instead, just query the accelerator for the 0xD leaf.
Do it in common code and clear esa->size if an extended save state is
unsupported.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
Link: https://lore.kernel.org/r/20241031085233.425388-3-tao1.su@linux.intel.com
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'module-common.c')
0 files changed, 0 insertions, 0 deletions