diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2025-07-25 01:10:12 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2025-07-25 14:51:11 +0200 |
| commit | feea87cd6b645d5166bdd304aac88f47f63dc2ef (patch) | |
| tree | d39b837c1e1b17d9fd539c997d9b592ac41ed5ce /rust/qemu-api/src | |
| parent | fbc8fb36e3636854195705cba13278befb94158d (diff) | |
| download | qemu-feea87cd6b645d5166bdd304aac88f47f63dc2ef.zip qemu-feea87cd6b645d5166bdd304aac88f47f63dc2ef.tar.gz qemu-feea87cd6b645d5166bdd304aac88f47f63dc2ef.tar.bz2 | |
target/i386: fix width of third operand of VINSERTx128
Table A-5 of the Intel manual incorrectly lists the third operand of
VINSERTx128 as Wqq, but it is actually a 128-bit value. This is
visible when W is a memory operand close to the end of the page.
Fixes the recently-added poly1305_kunit test in linux-next.
(No testcase yet, but I plan to modify test-avx2 to use memory
close to the end of the page. This would work because the test
vectors correctly have the memory operand as xmm2/m128).
Reported-by: Eric Biggers <ebiggers@kernel.org>
Tested-by: Eric Biggers <ebiggers@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: qemu-stable@nongnu.org
Fixes: 79068477686 ("target/i386: reimplement 0x0f 0x3a, add AVX", 2022-10-18)
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'rust/qemu-api/src')
0 files changed, 0 insertions, 0 deletions