about summary refs log tree commit diff
path: root/sysdeps/x86/fpu/powl_helper.c
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <siddhesh@sourceware.org>2017-10-23 20:22:42 +0530
committerSiddhesh Poyarekar <siddhesh@sourceware.org>2017-10-23 20:23:35 +0530
commita2e0a7f12ba57a49d1380c7ba1ff4b1f51d67347 (patch)
treee2082ffded8ed105c418278713345e4043b8b77e /sysdeps/x86/fpu/powl_helper.c
parentdb9bab09a51188bf57afeb47040ce6837b878367 (diff)
downloadglibc-a2e0a7f12ba57a49d1380c7ba1ff4b1f51d67347.tar.gz
glibc-a2e0a7f12ba57a49d1380c7ba1ff4b1f51d67347.tar.xz
glibc-a2e0a7f12ba57a49d1380c7ba1ff4b1f51d67347.zip
aarch64: Document _SC_LEVEL1_DCACHE_LINESIZE caveat
The _SC_LEVEL1_DCACHE_LINESIZE is reported using the contents of the
ctr_el0 register, which tells us the minimum observable cache line
size by userspace.  This typically is the same as the L1 cache line
size, but that may not always be true.  It could be a higher level
cache line size as long as cache cleaning and invalidation work
correctly with that line size in userspace.  The falkor core for
example reports the L2 line size as the dcache line size in CTR_EL0
while also reporting the correct L1 dcache line size via CCSIDR_EL1.

	* manual/conf.texi (_SC_LEVEL1_DCACHE_LINESIZE,
	_SC_LEVEL1_ICACHE_LINESIZE): Document aarch64 caveat.

Reviewed-by: Rical Jasan <ricaljasan@pacific.net>
Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
Diffstat (limited to 'sysdeps/x86/fpu/powl_helper.c')
0 files changed, 0 insertions, 0 deletions