Heiko Stuebner 56e0790c7f RISC-V: add infrastructure to allow different str* implementations ... Depending on supported extensions on specific RISC-V cores, optimized str* functions might make sense. This adds basic infrastructure to allow patching the function calls via alternatives later on. The Linux kernel provides standard implementations for string functions but when architectures want to extend them, they need to provide their own. The added generic string functions are done in assembler (taken from disassembling the main-kernel functions for now) to allow us to control the used registers and extend them with optimized variants. This doesn't override the compiler's use of builtin replacements. So still first of all the compiler will select if a builtin will be better suitable i.e. for known strings. For all regular cases we will want to later select possible optimized variants and in the worst case fall back to the generic implemention added with this change. Reviewed-by: Andrew Jones <ajones@ventanamicro.com> Signed-off-by: Heiko Stuebner <heiko.stuebner@vrull.eu> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20230113212301.3534711-2-heiko@sntech.de Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>		2023-01-31 11:43:23 -08:00
..
.gitignore	riscv/purgatory: Omit use of bin2c	2022-08-11 09:32:34 -07:00
entry.S	RISC-V: Add purgatory	2022-05-19 12:18:59 -07:00
kexec-purgatory.S	riscv/purgatory: Omit use of bin2c	2022-08-11 09:32:34 -07:00
Makefile	RISC-V: add infrastructure to allow different str* implementations	2023-01-31 11:43:23 -08:00
purgatory.c	RISC-V: Add purgatory	2022-05-19 12:18:59 -07:00