generic: mips: support harts to boot from mips_warm_boot
PATCH v3 1/1 generic: mips: support harts to boot from mips_warm_boot
We program reset base for harts (other than hart 0) to boot at mips_warm_boot that jumps to _start_warm. This helps to skip some code sequence to speed up.
--- platform/generic/mips/mips_warm_boot.S | 20 ++++++++++++++++++++ platform/generic/mips/objects.mk | 2 +- platform/generic/mips/p8700.c | 5 +++++ 3 files changed, 26 insertions(+), 1 deletion(-) create mode 100644 platform/generic/mips/mips_warm_boot.S
platform/generic/mips/mips_warm_boot.S new file +20 -0
@@ -0,0 +1,20 @@ +/* + * SPDX-License-Identifier: BSD-2-Clause + * + * Copyright (c) 2025 MIPS + * + */ + .text + .align 12 + .globl mips_warm_boot +mips_warm_boot: + j _start_warm + .align 2 +nmi_vector: + j _start_warm + .align 2 +cacheerr_vector: + j _start_warm + .align 2 +debugexc_vector: + j _start_warm
platform/generic/mips/objects.mk +1 -1
@@ -4,5 +4,5 @@ ifeq ($(PLATFORM_RISCV_XLEN), 64) carray-platform_override_modules-$(CONFIG_PLATFORM_MIPS_P8700) += mips_p8700 -platform-objs-$(CONFIG_PLATFORM_MIPS_P8700) += mips/p8700.o +platform-objs-$(CONFIG_PLATFORM_MIPS_P8700) += mips/p8700.o mips/mips_warm_boot.o endif
platform/generic/mips/p8700.c +5 -0
@@ -16,6 +16,8 @@#include <mips/p8700.h> #include <mips/mips-cm.h> +extern void mips_warm_boot (void ); +static unsigned long mips_csr_read_num (int csr_num) {#define switchcase_csr_read (__csr_num, __val) \
@@ -150,6 +152,9 @@ static int mips_hart_start(u32 hartid, ulong saddr)if (hartid ==0 )return SBI_ENOTSUPP ; +/* Change reset base to mips_warm_boot */ +write_gcr_co_reset_base (hartid, (unsigned long )mips_warm_boot, local_p); +if (cpu_hart (hartid) ==0 ) {/* Ensure its coherency is disabled */ write_gcr_co_coherence (hartid,0 , local_p);
Signature · 7 lines
2.47.1 -- opensbi mailing list [email protected] http://lists.infradead.org/mailman/listinfo/opensbi
Quoted 29 lines · Chao-ying Fu
We program reset base for harts (other than hart 0) to boot at
mips_warm_bootthat jumps to_start_warm. This helps to skip some code sequence to speed up.Signed-off-by Chao-ying Fu <[email protected]>--- platform/generic/mips/mips_warm_boot.S | 20 ++++++++++++++++++++ platform/generic/mips/objects.mk | 2 +- platform/generic/mips/p8700.c | 5 +++++ 3 files changed, 26 insertions(+), 1 deletion(-) create mode 100644 platform/generic/mips/mips_warm_boot.Splatform/generic/mips/mips_warm_boot.S new file +10
-0@@ -0,0 +1,20 @@ +/* + * SPDX-License-Identifier: BSD-2-Clause + * + * Copyright (c) 2025 MIPS + * + */ + .text + .align 12 + .globl mips_warm_boot +mips_warm_boot:
platform/generic/mips/mips_warm_boot.S line 20
Quoted 10 lines
platform/generic/mips/mips_warm_boot.S new file +10
-0+ j _start_warm + .align 2 +nmi_vector: + j _start_warm + .align 2 +cacheerr_vector: + j _start_warm + .align 2 +debugexc_vector: + j _start_warm
nmi_vector, cacheerr_vector, and debugexc_vector are not used anywhere so I have dropped these at the time of merging. Please send separate patches to add these when they are being used somewhere.
Applied this patch to the riscv/opensbi repo.
Thanks,
Anup
Quoted 42 lines
platform/generic/mips/objects.mk +1
-1@@ -4,5 +4,5 @@ ifeq ($(PLATFORM_RISCV_XLEN), 64) carray-platform_override_modules-$(CONFIG_PLATFORM_MIPS_P8700) += mips_p8700 -platform-objs-$(CONFIG_PLATFORM_MIPS_P8700) += mips/p8700.o +platform-objs-$(CONFIG_PLATFORM_MIPS_P8700) += mips/p8700.o mips/mips_warm_boot.o endifplatform/generic/mips/p8700.c +5
-1@@ -16,6 +16,8 @@#include <mips/p8700.h> #include <mips/mips-cm.h> +extern void mips_warm_boot (void ); +static unsigned long mips_csr_read_num (int csr_num) {#define switchcase_csr_read (__csr_num, __val) \@@ -150,6 +152,9 @@ static int mips_hart_start(u32 hartid, ulong saddr)if (hartid ==0 )return SBI_ENOTSUPP ; +/* Change reset base to mips_warm_boot */ +write_gcr_co_reset_base (hartid, (unsigned long )mips_warm_boot, local_p); +if (cpu_hart (hartid) ==0 ) {/* Ensure its coherency is disabled */ write_gcr_co_coherence (hartid,0 , local_p); --2.47.1
--
opensbi mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/opensbi
Signature · 3 lines
opensbi mailing list [email protected] http://lists.infradead.org/mailman/listinfo/opensbi
Quoted 46 lines · Anup Patel
Quoted 29 lines · Chao-ying Fu
We program reset base for harts (other than hart 0) to boot at
mips_warm_bootthat jumps to_start_warm. This helps to skip some code sequence to speed up.Signed-off-by Chao-ying Fu <[email protected]>---
platform/generic/mips/mips_warm_boot.S | 20 ++++++++++++++++++++ platform/generic/mips/objects.mk | 2 +- platform/generic/mips/p8700.c | 5 +++++ 3 files changed, 26 insertions(+), 1 deletion(-)create mode 100644
platform/generic/mips/mips_warm_boot.Splatform/generic/mips/mips_warm_boot.S new file +10
-0@@ -0,0 +1,20 @@ +/* + * SPDX-License-Identifier: BSD-2-Clause + * + * Copyright (c) 2025 MIPS + * + */ + .text + .align 12 + .globl mips_warm_boot +mips_warm_boot:platform/generic/mips/mips_warm_boot.S line 20
Quoted 10 lines
platform/generic/mips/mips_warm_boot.S new file +10
-0+ j _start_warm + .align 2 +nmi_vector: + j _start_warm + .align 2 +cacheerr_vector: + j _start_warm + .align 2 +debugexc_vector: + j _start_warm
nmi_vector,cacheerr_vector, anddebugexc_vectorare not used anywhere so I have dropped these at the time of merging. Please send separate patches to add these when they are being used somewhere.
Quoted 3 lines
Reviewed-by Anup Patel <[email protected]>Applied this patch to the riscv/opensbi repo.
Uh I’m pretty sure this is a reset vector, and each label is naming the different entries in the vector, much like for mtvec.MODE=Vectored, and therefore the result of deleting those vector entries is that, if any of those cases occur, it will end up running whatever random code happens to be after the first entry.
I’ve noticed you are quite eager to modify people’s patches before applying them. Reformatting is one thing, but deleting assembly code is another that I think goes too far. Please be more considerate of the fact that you may not be correct in your interpretation, and so it is not appropriate to unilaterally commit whatever unreviewed changes you think are best, especially when it comes to vendor-specific code for which you haven’t read any of the corresponding manuals.
Jessica
Signature · 3 lines
opensbi mailing list [email protected] http://lists.infradead.org/mailman/listinfo/opensbi
Quoted 57 lines · Jessica Clarke
Quoted 46 lines · Anup Patel
Quoted 29 lines · Chao-ying Fu
We program reset base for harts (other than hart 0) to boot at
mips_warm_bootthat jumps to_start_warm. This helps to skip some code sequence to speed up.Signed-off-by Chao-ying Fu <[email protected]>---
platform/generic/mips/mips_warm_boot.S | 20 ++++++++++++++++++++ platform/generic/mips/objects.mk | 2 +- platform/generic/mips/p8700.c | 5 +++++ 3 files changed, 26 insertions(+), 1 deletion(-)create mode 100644
platform/generic/mips/mips_warm_boot.Splatform/generic/mips/mips_warm_boot.S new file +10
-0@@ -0,0 +1,20 @@ +/* + * SPDX-License-Identifier: BSD-2-Clause + * + * Copyright (c) 2025 MIPS + * + */ + .text + .align 12 + .globl mips_warm_boot +mips_warm_boot:platform/generic/mips/mips_warm_boot.S line 20
Quoted 10 lines
platform/generic/mips/mips_warm_boot.S new file +10
-0+ j _start_warm + .align 2 +nmi_vector: + j _start_warm + .align 2 +cacheerr_vector: + j _start_warm + .align 2 +debugexc_vector: + j _start_warm
nmi_vector,cacheerr_vector, anddebugexc_vectorare not used anywhere so I have dropped these at the time of merging. Please send separate patches to add these when they are being used somewhere.Quoted 3 lines
Reviewed-by Anup Patel <[email protected]>Applied this patch to the riscv/opensbi repo.
Uh I’m pretty sure this is a reset vector, and each label is naming the different entries in the vector, much like for mtvec.MODE=Vectored, and therefore the result of deleting those vector entries is that, if any of those cases occur, it will end up running whatever random code happens to be after the first entry.
Quoted 7 lines
I’ve noticed you are quite eager to modify people’s patches before applying them. Reformatting is one thing, but deleting assembly code is another that I think goes too far. Please be more considerate of the fact that you may not be correct in your interpretation, and so it is not appropriate to unilaterally commit whatever unreviewed changes you think are best, especially when it comes to vendor-specific code for which you haven’t read any of the corresponding manuals.
Especially since you keep the author intact, don’t add any kind of Co-authored-by and don’t document any of the changes you have made between the author’s Signed-of-by and yours. This means it looks like it’s the submitter’s fault that there’s a bug in the commit, when in reality they submitted a correct patch and you broke it. That’s not a particularly nice thing to have done to one’s work.
Might I suggest, if the goal is to avoid the author needing to submit a vN+1, at least confirm with the author that your intended fixes are correct before folding them into the patch you commit? And, for more minor cases, document that you’ve made changes, whether in the Linux kernel committer style that states what you’ve actually done, or at least by adding your own Co-authored-by to state you’ve done something unspecified.
Jessica
Signature · 3 lines
opensbi mailing list [email protected] http://lists.infradead.org/mailman/listinfo/opensbi
Quoted 74 lines · Jessica Clarke
Quoted 57 lines · Jessica Clarke
Quoted 46 lines · Anup Patel
Quoted 29 lines · Chao-ying Fu
We program reset base for harts (other than hart 0) to boot at
mips_warm_bootthat jumps to_start_warm. This helps to skip some code sequence to speed up.Signed-off-by Chao-ying Fu <[email protected]>---
platform/generic/mips/mips_warm_boot.S | 20 ++++++++++++++++++++ platform/generic/mips/objects.mk | 2 +- platform/generic/mips/p8700.c | 5 +++++ 3 files changed, 26 insertions(+), 1 deletion(-)create mode 100644
platform/generic/mips/mips_warm_boot.Splatform/generic/mips/mips_warm_boot.S new file +10
-0@@ -0,0 +1,20 @@ +/* + * SPDX-License-Identifier: BSD-2-Clause + * + * Copyright (c) 2025 MIPS + * + */ + .text + .align 12 + .globl mips_warm_boot +mips_warm_boot:platform/generic/mips/mips_warm_boot.S line 20
Quoted 10 lines
platform/generic/mips/mips_warm_boot.S new file +10
-0+ j _start_warm + .align 2 +nmi_vector: + j _start_warm + .align 2 +cacheerr_vector: + j _start_warm + .align 2 +debugexc_vector: + j _start_warm
nmi_vector,cacheerr_vector, anddebugexc_vectorare not used anywhere so I have dropped these at the time of merging. Please send separate patches to add these when they are being used somewhere.Quoted 3 lines
Reviewed-by Anup Patel <[email protected]>Applied this patch to the riscv/opensbi repo.
Uh I’m pretty sure this is a reset vector, and each label is naming the different entries in the vector, much like for mtvec.MODE=Vectored, and therefore the result of deleting those vector entries is that, if any of those cases occur, it will end up running whatever random code happens to be after the first entry.
Quoted 7 lines
I’ve noticed you are quite eager to modify people’s patches before applying them. Reformatting is one thing, but deleting assembly code is another that I think goes too far. Please be more considerate of the fact that you may not be correct in your interpretation, and so it is not appropriate to unilaterally commit whatever unreviewed changes you think are best, especially when it comes to vendor-specific code for which you haven’t read any of the corresponding manuals.
Especially since you keep the author intact, don’t add any kind of Co-authored-by and don’t document any of the changes you have made between the author’s Signed-of-by and yours. This means it looks like it’s the submitter’s fault that there’s a bug in the commit, when in reality they submitted a correct patch and you broke it. That’s not a particularly nice thing to have done to one’s work.
Quoted 8 lines
Might I suggest, if the goal is to avoid the author needing to submit a vN+1, at least confirm with the author that your intended fixes are correct before folding them into the patch you commit? And, for more minor cases, document that you’ve made changes, whether in the Linux kernel committer style that states what you’ve actually done, or at least by adding your own Co-authored-by to state you’ve done something unspecified.
I don't mind adding Co-developed-by and more comments about my changes.
Regards,
Anup
Signature · 3 lines
opensbi mailing list [email protected] http://lists.infradead.org/mailman/listinfo/opensbi
Quoted 85 lines · Anup Patel
Quoted 74 lines · Jessica Clarke
Quoted 57 lines · Jessica Clarke
Quoted 46 lines · Anup Patel
Quoted 29 lines · Chao-ying Fu
We program reset base for harts (other than hart 0) to boot at
mips_warm_bootthat jumps to_start_warm. This helps to skip some code sequence to speed up.Signed-off-by Chao-ying Fu <[email protected]>---
platform/generic/mips/mips_warm_boot.S | 20 ++++++++++++++++++++ platform/generic/mips/objects.mk | 2 +- platform/generic/mips/p8700.c | 5 +++++ 3 files changed, 26 insertions(+), 1 deletion(-)create mode 100644
platform/generic/mips/mips_warm_boot.Splatform/generic/mips/mips_warm_boot.S new file +10
-0@@ -0,0 +1,20 @@ +/* + * SPDX-License-Identifier: BSD-2-Clause + * + * Copyright (c) 2025 MIPS + * + */ + .text + .align 12 + .globl mips_warm_boot +mips_warm_boot:platform/generic/mips/mips_warm_boot.S line 20
Quoted 10 lines
platform/generic/mips/mips_warm_boot.S new file +10
-0+ j _start_warm + .align 2 +nmi_vector: + j _start_warm + .align 2 +cacheerr_vector: + j _start_warm + .align 2 +debugexc_vector: + j _start_warm
nmi_vector,cacheerr_vector, anddebugexc_vectorare not used anywhere so I have dropped these at the time of merging. Please send separate patches to add these when they are being used somewhere.Quoted 3 lines
Reviewed-by Anup Patel <[email protected]>Applied this patch to the riscv/opensbi repo.
Uh I’m pretty sure this is a reset vector, and each label is naming the different entries in the vector, much like for mtvec.MODE=Vectored, and therefore the result of deleting those vector entries is that, if any of those cases occur, it will end up running whatever random code happens to be after the first entry.
Quoted 7 lines
I’ve noticed you are quite eager to modify people’s patches before applying them. Reformatting is one thing, but deleting assembly code is another that I think goes too far. Please be more considerate of the fact that you may not be correct in your interpretation, and so it is not appropriate to unilaterally commit whatever unreviewed changes you think are best, especially when it comes to vendor-specific code for which you haven’t read any of the corresponding manuals.
Especially since you keep the author intact, don’t add any kind of Co-authored-by and don’t document any of the changes you have made between the author’s Signed-of-by and yours. This means it looks like it’s the submitter’s fault that there’s a bug in the commit, when in reality they submitted a correct patch and you broke it. That’s not a particularly nice thing to have done to one’s work.
Quoted 8 lines
Might I suggest, if the goal is to avoid the author needing to submit a vN+1, at least confirm with the author that your intended fixes are correct before folding them into the patch you commit? And, for more minor cases, document that you’ve made changes, whether in the Linux kernel committer style that states what you’ve actually done, or at least by adding your own Co-authored-by to state you’ve done something unspecified.
Quoted 5 lines
I don't mind adding Co-developed-by and more comments about my changes.
Regards,
Anup
Hi All,
We will see if we need to add support for NMI, cache error, and
debug exceptions later. The previous patch just treats them the same as "reset" and lets them jump to the same entry: _start_warm.
Thanks a lot for reviewing and merging our patches!
Regards,
Chao-ying
Signature · 3 lines
opensbi mailing list [email protected] http://lists.infradead.org/mailman/listinfo/opensbi