openrisc: start CPU timer early in boot
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v8 6/19 openrisc: start CPU timer early in boot
In order to measure the boot process, the timer should be switched on as early in boot as possible. This is necessary so that by the time the setup code reaches random_init(), get_cycles() (by way of random_get_entropy()) returns non-zero, indicating that it is actually capable of counting. So this commit enables the timer immediately upon booting up. As well, the commit define the get_cycles macro, like the previous patches in this series, so that generic code is aware that it's implemented by the platform, as is done on other archs.
---
Changes v7->v8:
- Rather than doing get_cycles()+1 to handle the early boot case, actually start the timer early in boot. This has the huge advantage of properly measuring the boot sequence timing, which could be a valuable source of entropy.
arch/openrisc/include/asm/timex.h | 1 + arch/openrisc/kernel/setup.c | 7 +++++++ 2 files changed, 8 insertions(+)
arch/openrisc/include/asm/timex.h +1 -0
@@ -23,6 +23,7 @@ static inline cycles_t get_cycles(void) {return mfspr (SPR_TTCR ); } +#define get_cycles get_cycles/* This isn't really used any more */ #define CLOCK_TICK_RATE 1000
arch/openrisc/kernel/setup.c +7 -0
@@ -220,6 +220,13 @@ void __init setup_cpuinfo(void)void __init or1k_early_setup (void *fdt) { +/* Start the TTCR as early as possible, so that the RNG can make use of +* measurements of boot time from the earliest opportunity. Especially +* important is that the TTCR does not return zero by the time we reach +* rand_initialize(). +*/ +mtspr (SPR_TTMR ,SPR_TTMR_CR ); +if (fdt)pr_info ("FDT at %p\n" , fdt);else {
Signature · 1 line
2.35.1
Quoted 46 lines · Jason A. Donenfeld
In order to measure the boot process, the timer should be switched on as early in boot as possible. This is necessary so that by the time the setup code reaches
random_init(),get_cycles()(by way ofrandom_get_entropy()) returns non-zero, indicating that it is actually capable of counting. So this commit enables the timer immediately upon booting up. As well, the commit define theget_cyclesmacro, like the previous patches in this series, so that generic code is aware that it's implemented by the platform, as is done on other archs.Cc Thomas Gleixner <[email protected]>Cc Arnd Bergmann <[email protected]>Cc Jonas Bonn <[email protected]>Cc Stefan Kristiansson <[email protected]>Cc Stafford Horne <[email protected]>Signed-off-by Jason A. Donenfeld <[email protected]>---
Changesv7->v8:
- Rather than doing get_cycles()+1 to handle the early boot case, actually start the timer early in boot. This has the huge advantage of properly measuring the boot sequence timing, which could be a valuable source of entropy.arch/openrisc/include/asm/timex.h | 1 + arch/openrisc/kernel/setup.c | 7 +++++++ 2 files changed, 8 insertions(+)arch/openrisc/include/asm/timex.h +1
-0@@ -23,6 +23,7 @@ static inline cycles_t get_cycles(void) {return mfspr (SPR_TTCR ); } +#define get_cycles get_cycles/* This isn't really used any more */ #define CLOCK_TICK_RATE 1000arch/openrisc/kernel/setup.c +0
-0@@ -220,6 +220,13 @@ void __init setup_cpuinfo(void)void __init or1k_early_setup (void *fdt) {
arch/openrisc/kernel/setup.c void __init setup_cpuinfo(void) · line 232
Quoted 10 lines
arch/openrisc/kernel/setup.c +7
-0+/* Start the TTCR as early as possible, so that the RNG can make use of +* measurements of boot time from the earliest opportunity. Especially +* important is that the TTCR does not return zero by the time we reach +* rand_initialize(). +*/ +mtspr (SPR_TTMR ,SPR_TTMR_CR ); +if (fdt)pr_info ("FDT at %p\n" , fdt);else {
It looks like we cross paths on this one.
I can't think of anything better. Also, I tested this on SMP systems and it works fine.
Quoted 61 lines · Stafford Horne
Quoted 46 lines · Jason A. Donenfeld
In order to measure the boot process, the timer should be switched on as early in boot as possible. This is necessary so that by the time the setup code reaches
random_init(),get_cycles()(by way ofrandom_get_entropy()) returns non-zero, indicating that it is actually capable of counting. So this commit enables the timer immediately upon booting up. As well, the commit define theget_cyclesmacro, like the previous patches in this series, so that generic code is aware that it's implemented by the platform, as is done on other archs.Cc Thomas Gleixner <[email protected]>Cc Arnd Bergmann <[email protected]>Cc Jonas Bonn <[email protected]>Cc Stefan Kristiansson <[email protected]>Cc Stafford Horne <[email protected]>Signed-off-by Jason A. Donenfeld <[email protected]>---
Changesv7->v8:
- Rather than doing get_cycles()+1 to handle the early boot case, actually start the timer early in boot. This has the huge advantage of properly measuring the boot sequence timing, which could be a valuable source of entropy.arch/openrisc/include/asm/timex.h | 1 + arch/openrisc/kernel/setup.c | 7 +++++++ 2 files changed, 8 insertions(+)arch/openrisc/include/asm/timex.h +1
-0@@ -23,6 +23,7 @@ static inline cycles_t get_cycles(void) {return mfspr (SPR_TTCR ); } +#define get_cycles get_cycles/* This isn't really used any more */ #define CLOCK_TICK_RATE 1000arch/openrisc/kernel/setup.c +0
-0@@ -220,6 +220,13 @@ void __init setup_cpuinfo(void)void __init or1k_early_setup (void *fdt) {arch/openrisc/kernel/setup.c void __init setup_cpuinfo(void) · line 232
Quoted 10 lines
arch/openrisc/kernel/setup.c +7
-0+/* Start the TTCR as early as possible, so that the RNG can make use of +* measurements of boot time from the earliest opportunity. Especially +* important is that the TTCR does not return zero by the time we reach +* rand_initialize(). +*/ +mtspr (SPR_TTMR ,SPR_TTMR_CR ); +if (fdt)pr_info ("FDT at %p\n" , fdt);else {It looks like we cross paths on this one.
Quoted 4 lines
I can't think of anything better. Also, I tested this on SMP systems and it works fine.
Acked-by Stafford Horne <[email protected]>
Oh okay. Do you want me to go with this or with the assembly one?
Jason
PATCH v9 6/21 openrisc: start CPU timer early in boot
In order to measure the boot process, the timer should be switched on as early in boot as possible. This is necessary so that by the time the setup code reaches random_init(), get_cycles() (by way of random_get_entropy()) returns non-zero, indicating that it is actually capable of counting. So this commit enables the timer immediately upon booting up. As well, the commit define the get_cycles macro, like the previous patches in this series, so that generic code is aware that it's implemented by the platform, as is done on other archs.
---
Changes v8->v9:
- Use Stafford's suggested assembly in head.S instead of doing this later on in C, so that the cycle counter starts very early and thus "measures" boot.
arch/openrisc/include/asm/timex.h | 1 + arch/openrisc/kernel/head.S | 9 +++++++++ 2 files changed, 10 insertions(+)
arch/openrisc/include/asm/timex.h +1 -0
@@ -23,6 +23,7 @@ static inline cycles_t get_cycles(void) {return mfspr (SPR_TTCR ); } +#define get_cycles get_cycles/* This isn't really used any more */ #define CLOCK_TICK_RATE 1000
arch/openrisc/kernel/head.S +9 -0
@@ -521,6 +521,15 @@ _start: l.ori r3,r0,0x1 l.mtspr r0,r3,SPR_SR + /* + * Start the TTCR as early as possible, so that the RNG can make use of + * measurements of boot time from the earliest opportunity. Especially + * important is that the TTCR does not return zero by the time we reach + * rand_initialize(). + */ + l.movhi r3,hi(SPR_TTMR_CR) + l.mtspr r0,r3,SPR_TTMR + CLEAR_GPR(r1) CLEAR_GPR(r2) CLEAR_GPR(r3)
Signature · 1 line
2.35.1