diff options
author | Alexey Brodkin <[email protected]> | 2018-10-31 18:25:47 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2018-11-11 11:40:04 -0800 |
commit | a66d972465d15b1d89281258805eb8b47d66bd36 (patch) | |
tree | ec2a59ba96a3ab10277197653eb4c76d2a0825cb /tools/perf/scripts/python | |
parent | 651022382c7f8da46cb4872a545ee1da6d097d2a (diff) |
devres: Align data[] to ARCH_KMALLOC_MINALIGN
Initially we bumped into problem with 32-bit aligned atomic64_t
on ARC, see [1]. And then during quite lengthly discussion Peter Z.
mentioned ARCH_KMALLOC_MINALIGN which IMHO makes perfect sense.
If allocation is done by plain kmalloc() obtained buffer will be
ARCH_KMALLOC_MINALIGN aligned and then why buffer obtained via
devm_kmalloc() should have any other alignment?
This way we at least get the same behavior for both types of
allocation.
[1] http://lists.infradead.org/pipermail/linux-snps-arc/2018-July/004009.html
[2] http://lists.infradead.org/pipermail/linux-snps-arc/2018-July/004036.html
Signed-off-by: Alexey Brodkin <[email protected]>
Cc: Greg Kroah-Hartman <[email protected]>
Cc: Geert Uytterhoeven <[email protected]>
Cc: David Laight <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Vineet Gupta <[email protected]>
Cc: Will Deacon <[email protected]>
Cc: Greg KH <[email protected]>
Cc: <[email protected]> # 4.8+
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions