summaryrefslogtreecommitdiffstats
path: root/include/linux/task_io_accounting.h
diff options
context:
space:
mode:
authorDave Martin <dave.martin@linaro.org>2010-11-29 19:43:23 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2010-11-30 13:44:24 +0000
commit077248fcce5edabb1b77ba3269e6c72341769d94 (patch)
tree99a3ef92054ef39e63d39c56673f4db4c84c803d /include/linux/task_io_accounting.h
parent7eb25ebee894ba2f8a591a83e45accc091ced19f (diff)
downloadop-kernel-dev-077248fcce5edabb1b77ba3269e6c72341769d94.zip
op-kernel-dev-077248fcce5edabb1b77ba3269e6c72341769d94.tar.gz
ARM: 6499/1: Thumb-2: Correct data alignment for CONFIG_THUMB2_KERNEL in bootp/init.S
Directives such as .long and .word do not magically cause the assembler location counter to become aligned in gas. As a result, using these directives in code sections can result in misaligned data words when building a Thumb-2 kernel (CONFIG_THUMB2_KERNEL). This is a Bad Thing, since the ABI permits the compiler to assume that fundamental types of word size or above are word- aligned when accessing them from C. If the data is not really word-aligned, this can cause impaired performance and stray alignment faults in some circumstances. In general, the following rules should be applied when using data word declaration directives inside code sections: * .quad and .double: .align 3 * .long, .word, .single, .float: .align (or .align 2) * .short: No explicit alignment required, since Thumb-2 instructions are always 2 or 4 bytes in size. immediately after an instruction. Reviewed-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Dave Martin <dave.martin@linaro.org> Acked-by: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'include/linux/task_io_accounting.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud