If DCACHE_WORD_ACCESS is enabled big endian image failed to boot. commit 7bc13fd33adb9536bd73965cd46bbf7377df097c "arm64: dcache: select DCACHE_WORD_ACCESS for little-endian CPUs" enabled this setting for both big endian and little endian cpus. And code in commit itself seems to be endian agnostic, however other, i.e C, code that sits under DCACHE_WORD_ACCESS seems to be not endian agnostic, I could not figure out where though.
Solution is to enable DCACHE_WORD_ACCESS only if little endian mode is enabled (default).
Signed-off-by: Victor Kamensky victor.kamensky@linaro.org --- arch/arm64/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index e6e4d37..106ac4f 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -13,7 +13,7 @@ config ARM64 select CLONE_BACKWARDS select COMMON_CLK select CPU_PM if (SUSPEND || CPU_IDLE) - select DCACHE_WORD_ACCESS + select DCACHE_WORD_ACCESS if !CPU_BIG_ENDIAN select GENERIC_CLOCKEVENTS select GENERIC_CLOCKEVENTS_BROADCAST if SMP select GENERIC_CPU_AUTOPROBE
On Mon, Apr 21, 2014 at 11:36:10PM +0100, Victor Kamensky wrote:
If DCACHE_WORD_ACCESS is enabled big endian image failed to boot. commit 7bc13fd33adb9536bd73965cd46bbf7377df097c "arm64: dcache: select DCACHE_WORD_ACCESS for little-endian CPUs" enabled this setting for both big endian and little endian cpus. And code in commit itself seems to be endian agnostic, however other, i.e C, code that sits under DCACHE_WORD_ACCESS seems to be not endian agnostic, I could not figure out where though.
Solution is to enable DCACHE_WORD_ACCESS only if little endian mode is enabled (default).
Signed-off-by: Victor Kamensky victor.kamensky@linaro.org
NAK, this really should work for big-endian machines. If it doesn't, we should figure out why and fix the problem.
As a start, can you share further details of the failure please?
Will
arch/arm64/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index e6e4d37..106ac4f 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -13,7 +13,7 @@ config ARM64 select CLONE_BACKWARDS select COMMON_CLK select CPU_PM if (SUSPEND || CPU_IDLE)
- select DCACHE_WORD_ACCESS
- select DCACHE_WORD_ACCESS if !CPU_BIG_ENDIAN select GENERIC_CLOCKEVENTS select GENERIC_CLOCKEVENTS_BROADCAST if SMP select GENERIC_CPU_AUTOPROBE
-- 1.8.1.4
Hi Will,
On 22 April 2014 02:46, Will Deacon will.deacon@arm.com wrote:
On Mon, Apr 21, 2014 at 11:36:10PM +0100, Victor Kamensky wrote:
If DCACHE_WORD_ACCESS is enabled big endian image failed to boot. commit 7bc13fd33adb9536bd73965cd46bbf7377df097c "arm64: dcache: select DCACHE_WORD_ACCESS for little-endian CPUs" enabled this setting for both big endian and little endian cpus. And code in commit itself seems to be endian agnostic, however other, i.e C, code that sits under DCACHE_WORD_ACCESS seems to be not endian agnostic, I could not figure out where though.
Solution is to enable DCACHE_WORD_ACCESS only if little endian mode is enabled (default).
Signed-off-by: Victor Kamensky victor.kamensky@linaro.org
NAK, this really should work for big-endian machines. If it doesn't, we should figure out why and fix the problem.
Fair enough. Thanks for encouragement :)
As a start, can you share further details of the failure please?
Failure was that kernel could not find init in case of initramfs image or could not do nfs mount in nfs boot case ..
The issue turned out to be in another commit: "word-at-a-time: provide generic big-endian zero_bytemask implementation". Because of the issue in zero_bytemask function full_name_hash and hash_name were giving different hash results for the same path name (without slash). The issue is that (~0ul << 64) gives ~0ul not 0. I could not come up with more elegant solution other than use inline function that check shift value against type maximum width. Please take a look below.
The patch below is not correctly formatted because of my gmail client line wrapping issue, and others. I will resend it with git send-mail later. For now could you please take a look and maybe suggest something more nicer other than inline function and explicit check.
Also, if you can, could you please advise on what mailing list should I post it and who is appropriate maintainer. I could use get_maintainer.pl but would appreciate expert advice.
With below patch aarch64 big-endian image with DCACHE_WORD_ACCESS enabled boots OK.
From 47293e5e020ee8ad6233474a1eb13a149378de9d Mon Sep 17 00:00:00 2001
From: Victor Kamensky victor.kamensky@linaro.org Date: Tue, 22 Apr 2014 21:05:07 -0700 Subject: [PATCH] word-at-a-time: fix generic big-endian zero_bytemask in max width case
Commit 11ec50caedb56e3a87715edeff6a1852e6ae5416 "word-at-a-time: provide generic big-endian zero_bytemask implementation" added generic zero_bytemask implementation for big-endian system. But it gives incorrect result in case where fls gives shift value that equals to the width of unsigned long.
As per C standard left shifting for the full width of type is undefined: "If the value of the right operand is negative or is greater than or equal to the width of the promoted left operand, the behavior is undefined."
For example in arrach64 big-endian (~0ul << 64) will produce ~0ul. As result aarch64 big-endian is broken when CONFIG_DCACHE_WORD_ACCESS is defined and zero_bytemask is used.
Solution to check shift size and if it is equal to width of unsigned long return 0.
Signed-off-by: Victor Kamensky victor.kamensky@linaro.org --- include/asm-generic/word-at-a-time.h | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/include/asm-generic/word-at-a-time.h b/include/asm-generic/word-at-a-time.h index d3909ef..6c80ead 100644 --- a/include/asm-generic/word-at-a-time.h +++ b/include/asm-generic/word-at-a-time.h @@ -50,10 +50,20 @@ static inline bool has_zero(unsigned long val, unsigned long *data, const struct }
#ifndef zero_bytemask +static inline unsigned long __zero_bytemask(unsigned long shift) +{ + unsigned long ret; + if (shift != BITS_PER_LONG) + ret = (~0ul << shift); + else + ret = 0; + return ret; +} + #ifdef CONFIG_64BIT -#define zero_bytemask(mask) (~0ul << fls64(mask)) +#define zero_bytemask(mask) (__zero_bytemask(fls64(mask))) #else -#define zero_bytemask(mask) (~0ul << fls(mask)) +#define zero_bytemask(mask) (__zero_bytemask(fls(mask))) #endif /* CONFIG_64BIT */ #endif /* zero_bytemask */
On Wed, Apr 23, 2014 at 07:37:11AM +0100, Victor Kamensky wrote:
Hi Will,
Hi Victor,
Thanks for investigating this!
On 22 April 2014 02:46, Will Deacon will.deacon@arm.com wrote:
On Mon, Apr 21, 2014 at 11:36:10PM +0100, Victor Kamensky wrote:
The issue turned out to be in another commit: "word-at-a-time: provide generic big-endian zero_bytemask implementation". Because of the issue in zero_bytemask function full_name_hash and hash_name were giving different hash results for the same path name (without slash). The issue is that (~0ul << 64) gives ~0ul not 0. I could not come up with more elegant solution other than use inline function that check shift value against type maximum width. Please take a look below.
Ah yes, we're in UNDEFINED territory here and AArch64 differs from AArch32 wrt LSL >= register width. Can you try the following instead of your patch please? I think it should be more efficient.
Cheers,
Will
--->8
diff --git a/include/asm-generic/word-at-a-time.h b/include/asm-generic/word-at-a-time.h index d3909effd725..243ce8c84ee9 100644 --- a/include/asm-generic/word-at-a-time.h +++ b/include/asm-generic/word-at-a-time.h @@ -50,11 +50,7 @@ static inline bool has_zero(unsigned long val, unsigned long *data, const struct }
#ifndef zero_bytemask -#ifdef CONFIG_64BIT -#define zero_bytemask(mask) (~0ul << fls64(mask)) -#else -#define zero_bytemask(mask) (~0ul << fls(mask)) -#endif /* CONFIG_64BIT */ +#define zero_bytemask(mask) (mask ? ~0ul << __fls(mask) << 1 : ~0ul) #endif /* zero_bytemask */
#endif /* _ASM_WORD_AT_A_TIME_H */
On 23 April 2014 05:38, Will Deacon will.deacon@arm.com wrote:
On Wed, Apr 23, 2014 at 07:37:11AM +0100, Victor Kamensky wrote:
Hi Will,
Hi Victor,
Thanks for investigating this!
On 22 April 2014 02:46, Will Deacon will.deacon@arm.com wrote:
On Mon, Apr 21, 2014 at 11:36:10PM +0100, Victor Kamensky wrote:
The issue turned out to be in another commit: "word-at-a-time: provide generic big-endian zero_bytemask implementation". Because of the issue in zero_bytemask function full_name_hash and hash_name were giving different hash results for the same path name (without slash). The issue is that (~0ul << 64) gives ~0ul not 0. I could not come up with more elegant solution other than use inline function that check shift value against type maximum width. Please take a look below.
Ah yes, we're in UNDEFINED territory here and AArch64 differs from AArch32 wrt LSL >= register width. Can you try the following instead of your patch please? I think it should be more efficient.
Yes, it works. Checked initramfs and nfs boot with FVP. I knew you could do it way more elegant :).
How do we get it in? Do you want to commit/submit it yourself?
Thanks, Victor
Cheers,
Will
--->8
diff --git a/include/asm-generic/word-at-a-time.h b/include/asm-generic/word-at-a-time.h index d3909effd725..243ce8c84ee9 100644 --- a/include/asm-generic/word-at-a-time.h +++ b/include/asm-generic/word-at-a-time.h @@ -50,11 +50,7 @@ static inline bool has_zero(unsigned long val, unsigned long *data, const struct }
#ifndef zero_bytemask -#ifdef CONFIG_64BIT -#define zero_bytemask(mask) (~0ul << fls64(mask)) -#else -#define zero_bytemask(mask) (~0ul << fls(mask)) -#endif /* CONFIG_64BIT */ +#define zero_bytemask(mask) (mask ? ~0ul << __fls(mask) << 1 : ~0ul) #endif /* zero_bytemask */
#endif /* _ASM_WORD_AT_A_TIME_H */
On Wed, Apr 23, 2014 at 05:22:22PM +0100, Victor Kamensky wrote:
On 23 April 2014 05:38, Will Deacon will.deacon@arm.com wrote:
On Wed, Apr 23, 2014 at 07:37:11AM +0100, Victor Kamensky wrote:
Hi Will,
Hi Victor,
Thanks for investigating this!
On 22 April 2014 02:46, Will Deacon will.deacon@arm.com wrote:
On Mon, Apr 21, 2014 at 11:36:10PM +0100, Victor Kamensky wrote:
The issue turned out to be in another commit: "word-at-a-time: provide generic big-endian zero_bytemask implementation". Because of the issue in zero_bytemask function full_name_hash and hash_name were giving different hash results for the same path name (without slash). The issue is that (~0ul << 64) gives ~0ul not 0. I could not come up with more elegant solution other than use inline function that check shift value against type maximum width. Please take a look below.
Ah yes, we're in UNDEFINED territory here and AArch64 differs from AArch32 wrt LSL >= register width. Can you try the following instead of your patch please? I think it should be more efficient.
Yes, it works. Checked initramfs and nfs boot with FVP.
Hurrah!
I knew you could do it way more elegant :).
How do we get it in? Do you want to commit/submit it yourself?
I'll send a patch to LKML and see what Torvalds thinks. I've just come to the realisation that fs/namei.c will *never* call zero_bytemask with a mask == 0x0, so I'd like to remove the conditional altogether (which would be beneficial on AArch32).
I'll keep you on CC.
Cheers,
Will
linaro-kernel@lists.linaro.org
-
Victor Kamensky -
Will Deacon