riscv: Introduce alternative mechanism to apply errata solution
Introduce the "alternative" mechanism from ARM64 and x86 to apply the CPU
vendors' errata solution at runtime. The main purpose of this patch is
to provide a framework. Therefore, the implementation is quite basic for
now so that some scenarios could not use this schemei, such as patching
code to a module, relocating the patching code and heterogeneous CPU
topology.
Users could use the macro ALTERNATIVE to apply an errata to the existing
code flow. In the macro ALTERNATIVE, users need to specify the manufacturer
information(vendorid, archid, and impid) for this errata. Therefore, kernel
will know this errata is suitable for which CPU core. During the booting
procedure, kernel will select the errata required by the CPU core and then
patch it. It means that the kernel only applies the errata to the specified
CPU core. In this case, the vendor's errata does not affect each other at
runtime. The above patching procedure only occurs during the booting phase,
so we only take the overhead of the "alternative" mechanism once.
This "alternative" mechanism is enabled by default to ensure that all
required errata will be applied. However, users can disable this feature by
the Kconfig "CONFIG_RISCV_ERRATA_ALTERNATIVE".
Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
2021-03-22 22:26:03 +08:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
|
|
/*
|
|
|
|
* Copyright (C) 2021 Sifive.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __ASM_ALTERNATIVE_H
|
|
|
|
#define __ASM_ALTERNATIVE_H
|
|
|
|
|
|
|
|
#define ERRATA_STRING_LENGTH_MAX 32
|
|
|
|
|
|
|
|
#include <asm/alternative-macros.h>
|
|
|
|
|
|
|
|
#ifndef __ASSEMBLY__
|
|
|
|
|
2022-05-11 21:29:10 +02:00
|
|
|
#ifdef CONFIG_RISCV_ALTERNATIVE
|
|
|
|
|
riscv: Introduce alternative mechanism to apply errata solution
Introduce the "alternative" mechanism from ARM64 and x86 to apply the CPU
vendors' errata solution at runtime. The main purpose of this patch is
to provide a framework. Therefore, the implementation is quite basic for
now so that some scenarios could not use this schemei, such as patching
code to a module, relocating the patching code and heterogeneous CPU
topology.
Users could use the macro ALTERNATIVE to apply an errata to the existing
code flow. In the macro ALTERNATIVE, users need to specify the manufacturer
information(vendorid, archid, and impid) for this errata. Therefore, kernel
will know this errata is suitable for which CPU core. During the booting
procedure, kernel will select the errata required by the CPU core and then
patch it. It means that the kernel only applies the errata to the specified
CPU core. In this case, the vendor's errata does not affect each other at
runtime. The above patching procedure only occurs during the booting phase,
so we only take the overhead of the "alternative" mechanism once.
This "alternative" mechanism is enabled by default to ensure that all
required errata will be applied. However, users can disable this feature by
the Kconfig "CONFIG_RISCV_ERRATA_ALTERNATIVE".
Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
2021-03-22 22:26:03 +08:00
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/stddef.h>
|
|
|
|
#include <asm/hwcap.h>
|
|
|
|
|
2022-05-11 21:29:11 +02:00
|
|
|
#define RISCV_ALTERNATIVES_BOOT 0 /* alternatives applied during regular boot */
|
2022-05-11 21:29:12 +02:00
|
|
|
#define RISCV_ALTERNATIVES_MODULE 1 /* alternatives applied during module-init */
|
2022-05-11 21:29:21 +02:00
|
|
|
#define RISCV_ALTERNATIVES_EARLY_BOOT 2 /* alternatives applied before mmu start */
|
2022-05-11 21:29:11 +02:00
|
|
|
|
riscv: Introduce alternative mechanism to apply errata solution
Introduce the "alternative" mechanism from ARM64 and x86 to apply the CPU
vendors' errata solution at runtime. The main purpose of this patch is
to provide a framework. Therefore, the implementation is quite basic for
now so that some scenarios could not use this schemei, such as patching
code to a module, relocating the patching code and heterogeneous CPU
topology.
Users could use the macro ALTERNATIVE to apply an errata to the existing
code flow. In the macro ALTERNATIVE, users need to specify the manufacturer
information(vendorid, archid, and impid) for this errata. Therefore, kernel
will know this errata is suitable for which CPU core. During the booting
procedure, kernel will select the errata required by the CPU core and then
patch it. It means that the kernel only applies the errata to the specified
CPU core. In this case, the vendor's errata does not affect each other at
runtime. The above patching procedure only occurs during the booting phase,
so we only take the overhead of the "alternative" mechanism once.
This "alternative" mechanism is enabled by default to ensure that all
required errata will be applied. However, users can disable this feature by
the Kconfig "CONFIG_RISCV_ERRATA_ALTERNATIVE".
Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
2021-03-22 22:26:03 +08:00
|
|
|
void __init apply_boot_alternatives(void);
|
2022-05-11 21:29:21 +02:00
|
|
|
void __init apply_early_boot_alternatives(void);
|
2022-05-11 21:29:12 +02:00
|
|
|
void apply_module_alternatives(void *start, size_t length);
|
riscv: Introduce alternative mechanism to apply errata solution
Introduce the "alternative" mechanism from ARM64 and x86 to apply the CPU
vendors' errata solution at runtime. The main purpose of this patch is
to provide a framework. Therefore, the implementation is quite basic for
now so that some scenarios could not use this schemei, such as patching
code to a module, relocating the patching code and heterogeneous CPU
topology.
Users could use the macro ALTERNATIVE to apply an errata to the existing
code flow. In the macro ALTERNATIVE, users need to specify the manufacturer
information(vendorid, archid, and impid) for this errata. Therefore, kernel
will know this errata is suitable for which CPU core. During the booting
procedure, kernel will select the errata required by the CPU core and then
patch it. It means that the kernel only applies the errata to the specified
CPU core. In this case, the vendor's errata does not affect each other at
runtime. The above patching procedure only occurs during the booting phase,
so we only take the overhead of the "alternative" mechanism once.
This "alternative" mechanism is enabled by default to ensure that all
required errata will be applied. However, users can disable this feature by
the Kconfig "CONFIG_RISCV_ERRATA_ALTERNATIVE".
Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
2021-03-22 22:26:03 +08:00
|
|
|
|
|
|
|
struct alt_entry {
|
|
|
|
void *old_ptr; /* address of original instruciton or data */
|
|
|
|
void *alt_ptr; /* address of replacement instruction or data */
|
|
|
|
unsigned long vendor_id; /* cpu vendor id */
|
|
|
|
unsigned long alt_len; /* The replacement size */
|
|
|
|
unsigned int errata_id; /* The errata id */
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct errata_checkfunc_id {
|
|
|
|
unsigned long vendor_id;
|
|
|
|
bool (*func)(struct alt_entry *alt);
|
|
|
|
};
|
|
|
|
|
2021-03-22 22:26:04 +08:00
|
|
|
void sifive_errata_patch_func(struct alt_entry *begin, struct alt_entry *end,
|
2022-05-11 21:29:11 +02:00
|
|
|
unsigned long archid, unsigned long impid,
|
|
|
|
unsigned int stage);
|
2022-05-11 21:29:21 +02:00
|
|
|
void thead_errata_patch_func(struct alt_entry *begin, struct alt_entry *end,
|
|
|
|
unsigned long archid, unsigned long impid,
|
|
|
|
unsigned int stage);
|
2021-03-22 22:26:04 +08:00
|
|
|
|
2022-05-11 21:29:18 +02:00
|
|
|
void riscv_cpufeature_patch_func(struct alt_entry *begin, struct alt_entry *end,
|
|
|
|
unsigned int stage);
|
|
|
|
|
2022-05-11 21:29:10 +02:00
|
|
|
#else /* CONFIG_RISCV_ALTERNATIVE */
|
|
|
|
|
|
|
|
static inline void apply_boot_alternatives(void) { }
|
2022-05-11 21:29:21 +02:00
|
|
|
static inline void apply_early_boot_alternatives(void) { }
|
2022-05-11 21:29:12 +02:00
|
|
|
static inline void apply_module_alternatives(void *start, size_t length) { }
|
2022-05-11 21:29:10 +02:00
|
|
|
|
|
|
|
#endif /* CONFIG_RISCV_ALTERNATIVE */
|
|
|
|
|
riscv: Introduce alternative mechanism to apply errata solution
Introduce the "alternative" mechanism from ARM64 and x86 to apply the CPU
vendors' errata solution at runtime. The main purpose of this patch is
to provide a framework. Therefore, the implementation is quite basic for
now so that some scenarios could not use this schemei, such as patching
code to a module, relocating the patching code and heterogeneous CPU
topology.
Users could use the macro ALTERNATIVE to apply an errata to the existing
code flow. In the macro ALTERNATIVE, users need to specify the manufacturer
information(vendorid, archid, and impid) for this errata. Therefore, kernel
will know this errata is suitable for which CPU core. During the booting
procedure, kernel will select the errata required by the CPU core and then
patch it. It means that the kernel only applies the errata to the specified
CPU core. In this case, the vendor's errata does not affect each other at
runtime. The above patching procedure only occurs during the booting phase,
so we only take the overhead of the "alternative" mechanism once.
This "alternative" mechanism is enabled by default to ensure that all
required errata will be applied. However, users can disable this feature by
the Kconfig "CONFIG_RISCV_ERRATA_ALTERNATIVE".
Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
2021-03-22 22:26:03 +08:00
|
|
|
#endif
|
|
|
|
#endif
|