[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 07/16] target/arm: Align vector registers
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [Qemu-devel] [PATCH v2 07/16] target/arm: Align vector registers |
Date: |
Tue, 12 Sep 2017 17:44:43 -0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
- float64 regs[64];
+ float64 regs[64] __attribute__((aligned(16)));
I understand this should be aligned to the biggest vector register the
host support, i.e. for AVX-512 this would be QEMU_ALIGNED(64), is it
correct?
checking datashits:
"INTEL® ADVANCED VECTOR EXTENSIONS"
2.5 MEMORY ALIGNMENT
With the exception of explicitly aligned 16 or 32 byte SIMD load/store
instructions, most VEX-encoded, arithmetic and data processing
instructions operate in a flexible environment regarding memory address
alignment, i.e. VEX-encoded instruction with 32-byte or 16-byte load
semantics will support unaligned load operation by default. Memory
arguments for most instructions with VEX prefix operate normally without
causing #GP(0) on any byte-granularity alignment (unlike Legacy SSE
instructions). The instructions that require explicit memory alignment
requirements are listed in Table 2-4.
Table 2-4. Instructions Requiring Explicitly Aligned Memory
Require 32-byte alignment:
VMOVDQA ymm, m256
VMOVDQA m256, ymm
VMOVAPS ymm, m256
VMOVAPS m256, ymm
VMOVAPD ymm, m256
VMOVAPD m256, ymm
VMOVNTPS m256, ymm
VMOVNTPD m256, ymm
VMOVNTDQ m256, ymm
VMOVNTDQA ymm, m256
General Protection, #GP(0):
VEX.256: Memory operand is not 32-byte aligned
VEX.128: Memory operand is not 16-byte aligned
Legacy SSE: Memory operand is not 16-byte aligned
--
"Intel® Architecture Instruction Set Extensions Programming Reference"
2.6 MEMORY ALIGNMENT
Memory alignment requirements on EVEX-encoded SIMD instructions are
similar to VEX-encoded SIMD instructions. Memory alignment applies to
EVEX-encoded SIMD instructions in three categories:
• Explicitly-aligned SIMD load and store instructions accessing 64 bytes
of memory with EVEX prefix encoded vector length of 512 bits (e.g.,
VMOVAPD, VMOVAPS, VMOVDQA, etc.). These instructions always require
memory address to be aligned on 64-byte boundary.
• Explicitly-unaligned SIMD load and store instructions accessing 64
bytes or less of data from memory (e.g. VMOVUPD, VMOVUPS, VMOVDQU,
VMOVQ, VMOVD, etc.). These instructions do not require memory address
to be aligned on natural vector-length byte boundary.
• Most arithmetic and data processing instructions encoded using EVEX
support memory access semantics. When these instructions access from
memory, there are no alignment restrictions.
[...]
AVX-512 instructions may generate an #AC(0) fault on misaligned 4 or
8-byte memory references in Ring-3 when CR0.AM=1. 16, 32 and 64-byte
memory references will not generate #AC(0) fault. See Table 2-7 for details.
Certain AVX-512 Foundation instructions always require 64-byte alignment
(see the complete list of VEX and EVEX encoded instructions in Table
2-6). These instructions will #GP(0) if not aligned to 64-byte boundaries.
- [Qemu-devel] [PATCH v2 00/16] TCG vectorization and example conversion, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 01/16] tcg: Add expanders for out-of-line vector helpers, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 02/16] tcg: Add types for host vectors, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 03/16] tcg: Add operations for host vectors, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 05/16] tcg: Add INDEX_op_invalid, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 04/16] tcg: Add tcg_op_supported, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 07/16] target/arm: Align vector registers, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 06/16] tcg: Add vector infrastructure and ops for add/sub/logic, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 08/16] target/arm: Use vector infrastructure for aa64 add/sub/logic, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 10/16] tcg/aarch64: Fully convert tcg_target_op_def, Richard Henderson, 2017/09/12
- [Qemu-devel] [PATCH v2 12/16] tcg: Remove tcg_regset_set, Richard Henderson, 2017/09/12