Simplify cpu initialization
cover Simplify cpu initialization
Currently, there are pieces of cpu initialization being done in two different places. The big part of it, is done inside cpu_x86_init, while minor others are done in pc.c, after cpu_x86_init returns.
For things like halting cpus != 0, registering reset handler, etc, there is no reason whatsoever for not doing it in cpu initialization.
The apic initialization should be moved there too, and theorectically, it should not depend on pci machine. However, it currently breaks our isa machine, and to avoid a hack, it is left where it is.
PATCH 1/4 move registering of cpu_reset to inside cpu_init
This is not pc specific by any means. So we can be moved to inside cpu_x86_init().
This is part of an attempt to only initialize kvm state after everything is already properly initialized. If we don't do that, we can race against, for example, APIC state if kvm vcpus are ran in threads (happens in qemu-kvm.git, soon to happen here too)
--- hw/pc.c | 7 ------- target-i386/helper.c | 8 ++++++++ 2 files changed, 8 insertions(+), 7 deletions(-)
hw/pc.c +0 -7
@@ -725,12 +725,6 @@ static void load_linux(target_phys_addr_t option_rom,generate_bootsect (option_rom, gpr, seg,0 ); } -static void main_cpu_reset (void *opaque) -{ -CPUState *env = opaque; -cpu_reset (env); -} -static const int ide_iobase[2 ] = {0x1f0 ,0x170 };static const int ide_iobase2[2 ] = {0x3f6 ,0x376 };static const int ide_irq[2 ] = {14 ,15 };
@@ -861,7 +855,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size,/* XXX: enable it in all cases */ env->cpuid_features |=CPUID_APIC ; } -qemu_register_reset (main_cpu_reset, env);if (pci_enabled) {apic_init (env); }
target-i386/helper.c +8 -0
@@ -29,6 +29,7 @@#include "exec-all.h" #include "qemu-common.h" #include "kvm.h" +#include "hw/hw.h" //#define DEBUG_MMU
@@ -507,6 +508,11 @@ void cpu_reset(CPUX86State *env)cpu_watchpoint_remove_all (env,BP_CPU ); } +static void main_cpu_reset (void *_env) +{ +cpu_reset ((CPUState *)_env); +} +void cpu_x86_close (CPUX86State *env) {qemu_free (env);
@@ -1689,6 +1695,8 @@ CPUX86State *cpu_x86_init(const char *cpu_model)return NULL ; }cpu_reset (env); +qemu_register_reset (main_cpu_reset, env); +#ifdef CONFIG_KQEMU kqemu_init (env);#endif
Signature · 1 line
1.5.6.6
PATCH 2/4 move CPUID_APIC flag to where it belongs
We can safely do that inconditionally, so move to processor defined flags like any other flag.
--- hw/pc.c | 4 ---- target-i386/helper.c | 2 +- 2 files changed, 1 insertions(+), 5 deletions(-)
hw/pc.c +0 -4
@@ -851,10 +851,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size, }if (i !=0 ) env->halted =1 ; -if (smp_cpus >1 ) { -/* XXX: enable it in all cases */ - env->cpuid_features |=CPUID_APIC ; - }if (pci_enabled) {apic_init (env); }
target-i386/helper.c +1 -1
@@ -102,7 +102,7 @@ typedef struct x86_def_t {char model_id[48 ]; } x86_def_t; -#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE) +#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE | CPUID_APIC)#define PENTIUM_FEATURES (I486_FEATURES | CPUID_DE | CPUID_TSC | \ CPUID_MSR | CPUID_MCE | CPUID_CX8 | CPUID_MMX)#define PENTIUM2_FEATURES (PENTIUM_FEATURES | CPUID_PAE | CPUID_SEP | \
Signature · 1 line
1.5.6.6
PATCH 3/4 move halted state setting to inside of cpu_x86_init
cpus other than the first one starting at the halted state is a safe assumption to anyone. Move it to where it belongs.
--- hw/pc.c | 2 -- target-i386/helper.c | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-)
hw/pc.c +0 -2
@@ -849,8 +849,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size,fprintf (stderr,"Unable to find x86 CPU definition\n" );exit (1 ); } -if (i !=0 ) - env->halted =1 ;if (pci_enabled) {apic_init (env); }
target-i386/helper.c +3 -0
@@ -1694,6 +1694,9 @@ CPUX86State *cpu_x86_init(const char *cpu_model)cpu_x86_close (env);return NULL ; } + +/* cpu 0 can run, others start at halted state */ + env->halted = !!env->cpu_index;cpu_reset (env);qemu_register_reset (main_cpu_reset, env);
Signature · 1 line
1.5.6.6
PATCH 4/4 move apic functions to a separate apic.h header
Later on, we'll want to call an apic function from helper.c. The inclusion of pc.h, besides totally ugly, leads to a lot of clashes.
--- hw/apic.c | 1 + hw/apic.h | 19 +++++++++++++++++++ hw/ioapic.c | 1 + hw/mc146818rtc.c | 1 + hw/pc.c | 1 + hw/pc.h | 15 --------------- 6 files changed, 23 insertions(+), 15 deletions(-) create mode 100644 hw/apic.h
hw/apic.c +1 -0
@@ -19,6 +19,7 @@*/ #include "hw.h" #include "pc.h" +#include "apic.h" #include "qemu-timer.h" #include "host-utils.h"
hw/apic.h new file +19 -0
@@ -0,0 +1,19 @@ +#ifndef _APIC_H_ +#define _APIC_H_ + +/* APIC */ +typedef struct IOAPICState IOAPICState ; +void apic_deliver_irq (uint8_t dest,uint8_t dest_mode, +uint8_t delivery_mode, +uint8_t vector_num,uint8_t polarity, +uint8_t trigger_mode); +int apic_init (CPUState *env); +int apic_accept_pic_intr (CPUState *env); +void apic_deliver_pic_intr (CPUState *env,int level); +int apic_get_interrupt (CPUState *env); +IOAPICState *ioapic_init (void ); +void ioapic_set_irq (void *opaque,int vector,int level); +void apic_reset_irq_delivered (void ); +int apic_get_irq_delivered (void ); + +#endif
hw/ioapic.c +1 -0
@@ -22,6 +22,7 @@*/ #include "hw.h" +#include "apic.h" #include "pc.h" #include "qemu-timer.h" #include "host-utils.h"
hw/mc146818rtc.c +1 -0
@@ -25,6 +25,7 @@#include "qemu-timer.h" #include "sysemu.h" #include "pc.h" +#include "apic.h" #include "isa.h" #include "hpet_emul.h"
hw/pc.c +1 -0
@@ -23,6 +23,7 @@*/ #include "hw.h" #include "pc.h" +#include "apic.h" #include "fdc.h" #include "pci.h" #include "block.h"
hw/pc.h +0 -15
@@ -40,21 +40,6 @@ uint32_t pic_intack_read(PicState2 *s);void pic_info (Monitor *mon);void irq_info (Monitor *mon); -/* APIC */ -typedef struct IOAPICState IOAPICState ; -void apic_deliver_irq (uint8_t dest,uint8_t dest_mode, -uint8_t delivery_mode, -uint8_t vector_num,uint8_t polarity, -uint8_t trigger_mode); -int apic_init (CPUState *env); -int apic_accept_pic_intr (CPUState *env); -void apic_deliver_pic_intr (CPUState *env,int level); -int apic_get_interrupt (CPUState *env); -IOAPICState *ioapic_init (void ); -void ioapic_set_irq (void *opaque,int vector,int level); -void apic_reset_irq_delivered (void ); -int apic_get_irq_delivered (void ); -/* i8254.c */ #define PIT_FREQ 1193182
Signature · 1 line
1.5.6.6
[Qemu-devel] Re: [PATCH 4/4] move apic functions to a separate apic.h header
Quoted 20 lines · Glauber Costa
Later on, we'll want to call an apic function from
helper.c. The inclusion ofpc.h, besides totally ugly, leads to a lot of clashes.Signed-off-by Glauber Costa <[email protected]>--- hw/apic.c | 1 + hw/apic.h | 19 +++++++++++++++++++ hw/ioapic.c | 1 + hw/mc146818rtc.c | 1 + hw/pc.c | 1 + hw/pc.h | 15 --------------- 6 files changed, 23 insertions(+), 15 deletions(-) create mode 100644 hw/apic.hhw/apic.c +0
-0
hw/apic.c line 22
Quoted 4 lines
hw/apic.c +1
-0@@ -19,6 +19,7 @@*/ #include "hw.h" #include "pc.h" +#include "apic.h"
Does it still need pc.h then?
hw/apic.h line 2
Quoted 11 lines
hw/apic.c +0
-0#include "qemu-timer.h" #include "host-utils.h" hw/apic.h new file +2
-0@@ -0,0 +1,19 @@ +#ifndef _APIC_H_ +#define _APIC_H_
"APIC_H", otherwise fine.
Quoted 69 lines
hw/apic.h new file +17
-0+ +/* APIC */ +typedef struct IOAPICState IOAPICState ; +void apic_deliver_irq (uint8_t dest,uint8_t dest_mode, +uint8_t delivery_mode, +uint8_t vector_num,uint8_t polarity, +uint8_t trigger_mode); +int apic_init (CPUState *env); +int apic_accept_pic_intr (CPUState *env); +void apic_deliver_pic_intr (CPUState *env,int level); +int apic_get_interrupt (CPUState *env); +IOAPICState *ioapic_init (void ); +void ioapic_set_irq (void *opaque,int vector,int level); +void apic_reset_irq_delivered (void ); +int apic_get_irq_delivered (void ); + +#endif hw/ioapic.c +1
-0@@ -22,6 +22,7 @@*/ #include "hw.h" +#include "apic.h" #include "pc.h" #include "qemu-timer.h" #include "host-utils.h" hw/mc146818rtc.c +1
-0@@ -25,6 +25,7 @@#include "qemu-timer.h" #include "sysemu.h" #include "pc.h" +#include "apic.h" #include "isa.h" #include "hpet_emul.h" hw/pc.c +1
-0@@ -23,6 +23,7 @@*/ #include "hw.h" #include "pc.h" +#include "apic.h" #include "fdc.h" #include "pci.h" #include "block.h" hw/pc.h +0
-8@@ -40,21 +40,6 @@ uint32_t pic_intack_read(PicState2 *s);void pic_info (Monitor *mon);void irq_info (Monitor *mon); -/* APIC */ -typedef struct IOAPICState IOAPICState ; -void apic_deliver_irq (uint8_t dest,uint8_t dest_mode, -uint8_t delivery_mode, -uint8_t vector_num,uint8_t polarity, -uint8_t trigger_mode); -int apic_init (CPUState *env); -int apic_accept_pic_intr (CPUState *env);
hw/pc.h uint32_t pic_intack_read(PicState2 *s); · line 45
Quoted 10 lines
hw/pc.h +0
-7-void apic_deliver_pic_intr (CPUState *env,int level); -int apic_get_interrupt (CPUState *env); -IOAPICState *ioapic_init (void ); -void ioapic_set_irq (void *opaque,int vector,int level); -void apic_reset_irq_delivered (void ); -int apic_get_irq_delivered (void ); -/* i8254.c */ #define PIT_FREQ 1193182
Jan
Signature · 2 lines
Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux
[Qemu-devel] Re: [PATCH 4/4] move apic functions to a separate apic.h header
Quoted 16 lines · Jan Kiszka
Quoted 15 lines · Glauber Costa
Later on, we'll want to call an apic function from
helper.c. The inclusion ofpc.h, besides totally ugly, leads to a lot of clashes.Signed-off-by Glauber Costa <[email protected]>--- hw/apic.c | 1 + hw/apic.h | 19 +++++++++++++++++++ hw/ioapic.c | 1 + hw/mc146818rtc.c | 1 + hw/pc.c | 1 + hw/pc.h | 15 --------------- 6 files changed, 23 insertions(+), 15 deletions(-) create mode 100644 hw/apic.h
Quoted 11 lines
hw/apic.c line 22
Quoted 9 lines
hw/apic.c +1
-0@@ -19,6 +19,7 @@*/ #include "hw.h" #include "pc.h" +#include "apic.h" Does it still need
pc.hthen?
yes. For things like RTCState.
Quoted 4 lines
Quoted 4 lines
hw/apic.c +0
-0#include "qemu-timer.h" #include "host-utils.h"
Quoted 10 lines
hw/apic.h line 2
Quoted 8 lines
hw/apic.h new file +2
-0@@ -0,0 +1,19 @@ +#ifndef _APIC_H_ +#define _APIC_H_"
APIC_H", otherwise fine.
ok.
[Qemu-devel] Re: [PATCH 3/4] move halted state setting to inside of cpu_x86_init
In reply to Glauber CostaQuoted 27 lines · Glauber Costa
cpus other than the first one starting at the halted state is a safe assumption to anyone. Move it to where it belongs.
Signed-off-by Glauber Costa <[email protected]>--- hw/pc.c | 2 -- target-i386/helper.c | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-)hw/pc.c +0
-2@@ -849,8 +849,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size,fprintf (stderr,"Unable to find x86 CPU definition\n" );exit (1 ); } -if (i !=0 ) - env->halted =1 ;if (pci_enabled) {apic_init (env); }target-i386/helper.c +0
-0
target-i386/helper.c CPUX86State *cpu_x86_init(const char *cpu_model) · line 1702
Quoted 9 lines
target-i386/helper.c +3
-0@@ -1694,6 +1694,9 @@ CPUX86State *cpu_x86_init(const char *cpu_model)cpu_x86_close (env);return NULL ; } + +/* cpu 0 can run, others start at halted state */ + env->halted = !!env->cpu_index;cpu_reset (env);qemu_register_reset (main_cpu_reset, env);
That looks good to me.
Jan
Signature · 2 lines
Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux
Re: [Qemu-devel] [PATCH 3/4] move halted state setting to inside of cpu_x86_init
In reply to Glauber CostaQuoted 2 lines · Glauber Costa
cpus other than the first one starting at the halted state
is a safe assumption to anyone. Move it to where it belongs.
The code should be conditional to !CONFIG_USER_ONLY.
The same happens with Sparc, so I'd move this to exec.c:cpu_exec_init().
Re: [Qemu-devel] [PATCH 3/4] move halted state setting to inside of cpu_x86_init
Quoted 5 lines · Blue Swirl
Quoted 2 lines · Glauber Costa
cpus other than the first one starting at the halted state
is a safe assumption to anyone. Move it to where it belongs.The code should be conditional to !CONFIG_USER_ONLY.
Fine.
Quoted 2 lines
The same happens with Sparc, so I'd move this to exec.c:cpu_exec_init().
It would be indeed, better.
Anyone from other arches opposes to this?
[Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
In reply to Glauber CostaQuoted 29 lines · Glauber Costa
We can safely do that inconditionally, so move to processor defined flags like any other flag.
Signed-off-by Glauber Costa <[email protected]>--- hw/pc.c | 4 ---- target-i386/helper.c | 2 +- 2 files changed, 1 insertions(+), 5 deletions(-)hw/pc.c +0
-4@@ -851,10 +851,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size, }if (i !=0 ) env->halted =1 ; -if (smp_cpus >1 ) { -/* XXX: enable it in all cases */ - env->cpuid_features |=CPUID_APIC ; - }if (pci_enabled) {apic_init (env); }target-i386/helper.c +0
-0
target-i386/helper.c typedef struct x86_def_t { · line 105
Quoted 5 lines
target-i386/helper.c +1
-1@@ -102,7 +102,7 @@ typedef struct x86_def_t {char model_id[48 ]; } x86_def_t; -#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE) +#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE | CPUID_APIC)
Without doing my homework:
What impact will it have on an emulated CPUs without [L]APIC? I'm thinking of -M isapc e.g.
Jan
Signature · 2 lines
Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux
[Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
Quoted 33 lines · Jan Kiszka
Quoted 32 lines · Glauber Costa
We can safely do that inconditionally, so move to processor defined flags like any other flag.
Signed-off-by Glauber Costa <[email protected]>--- hw/pc.c | 4 ---- target-i386/helper.c | 2 +- 2 files changed, 1 insertions(+), 5 deletions(-)hw/pc.c +0
-4@@ -851,10 +851,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size, }if (i !=0 ) env->halted =1 ; -if (smp_cpus >1 ) { -/* XXX: enable it in all cases */ - env->cpuid_features |=CPUID_APIC ; - }if (pci_enabled) {apic_init (env); }target-i386/helper.c +0
-0@@ -102,7 +102,7 @@ typedef struct x86_def_t {char model_id[48 ]; } x86_def_t;
Quoted 6 lines
target-i386/helper.c typedef struct x86_def_t { · line 105
Quoted 2 lines
target-i386/helper.c +1
-1-#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE) +#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE | CPUID_APIC)Without doing my homework:
What impact will it have on an emulated CPUs without [L]APIC? I'm thinking of -M isapc e.g.
I tried, and it still boots fine.
The flag just indicates it supports an apic, not that it has one.
RE: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
If OS boot fine its more luck. The flag indicates presence of local apic, not "if it is supported".
For example when lapic is globally disabled (i.e. not present) CPUID flag is cleared off as well.
But CPU is still supports lapic, after reset it will be back.
Stanislav
Quoted 7 lines
Without doing my homework:
What impact will it have on an emulated CPUs without [L]APIC? I'm thinking of -M isapc e.g.I tried, and it still boots fine.
The flag just indicates it supports an apic, not that it has one.
Re: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
Quoted 5 lines · Stanislav
If OS boot fine its more luck. The flag indicates presence of local apic, not "if it is supported".
For example when lapic is globally disabled (i.e. not present) CPUID flag is cleared off as well.
But CPU is still supports lapic, after reset it will be back.
What if we take out a cpu that supports lapic, and is connected to an apic system, and connects it to a board that has no apic?
Also, note that in the old code, it was set regardless of the existance of an APIC anyway. The only dependancy was on smp_cpus > 1.
RE: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
Local apic and i/o apic are not really related.
Local apic is actually a cpu feature, not optional external peripheral. I/O apic is external hardware on board and if you don't have it - you can't program your interrupts that much.
I am not telling if a patch is wrong/better than it was before - just want to point out how it really works.
Stanislav
-----Original Message-----
From: Glauber Costa [mailto:[email protected]]
Sent: Wednesday, May 06, 2009 8:42 PM
To: Stanislav
Cc: 'Jan Kiszka'; [email protected]; [email protected]
Subject: Re: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
Quoted 3 lines · Stanislav
If OS boot fine its more luck. The flag indicates presence of local apic, not "if it is supported".
For example when lapic is globally disabled (i.e. not present) CPUID flag
is
Quoted 2 lines
cleared off as well.
But CPU is still supports lapic, after reset it will be back.
What if we take out a cpu that supports lapic, and is connected to an apic system,
and connects it to a board that has no apic?
Also, note that in the old code, it was set regardless of the existance of an APIC
anyway. The only dependancy was on smp_cpus > 1.
Re: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
In reply to StanislavQuoted 3 lines · Stanislav
If OS boot fine its more luck. The flag indicates presence of local apic, not "if it is supported".
But having a local apic present in an isapc should not cause any problems as it's backwards compatible with the pic.
But yeah, there really isn't a "is supported" flag. It's either there or it's not.
Regards,
Anthony Liguori
[Qemu-devel] Re: [PATCH 1/4] move registering of cpu_reset to inside cpu_init
In reply to Glauber CostaQuoted 64 lines · Glauber Costa
This is not pc specific by any means. So we can be moved to inside
cpu_x86_init().This is part of an attempt to only initialize kvm state after everything is already properly initialized. If we don't do that, we can race against, for example, APIC state if kvm vcpus are ran in threads (happens in qemu-kvm.git, soon to happen here too)
Signed-off-by Glauber Costa <[email protected]>--- hw/pc.c | 7 ------- target-i386/helper.c | 8 ++++++++ 2 files changed, 8 insertions(+), 7 deletions(-)hw/pc.c +0
-7@@ -725,12 +725,6 @@ static void load_linux(target_phys_addr_t option_rom,generate_bootsect (option_rom, gpr, seg,0 ); } -static void main_cpu_reset (void *opaque) -{ -CPUState *env = opaque; -cpu_reset (env); -} -static const int ide_iobase[2 ] = {0x1f0 ,0x170 };static const int ide_iobase2[2 ] = {0x3f6 ,0x376 };static const int ide_irq[2 ] = {14 ,15 };@@ -861,7 +855,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size,/* XXX: enable it in all cases */ env->cpuid_features |=CPUID_APIC ; } -qemu_register_reset (main_cpu_reset, env);if (pci_enabled) {apic_init (env); }target-i386/helper.c +6
-0@@ -29,6 +29,7 @@#include "exec-all.h" #include "qemu-common.h" #include "kvm.h" +#include "hw/hw.h" //#define DEBUG_MMU @@ -507,6 +508,11 @@ void cpu_reset(CPUX86State *env)cpu_watchpoint_remove_all (env,BP_CPU ); } +static void main_cpu_reset (void *_env) +{ +cpu_reset ((CPUState *)_env); +} +void cpu_x86_close (CPUX86State *env) {qemu_free (env);
target-i386/helper.c CPUX86State *cpu_x86_init(const char *cpu_model) · line 1702
Quoted 8 lines
target-i386/helper.c +2
-0@@ -1689,6 +1695,8 @@ CPUX86State *cpu_x86_init(const char *cpu_model)return NULL ; }cpu_reset (env); +qemu_register_reset (main_cpu_reset, env); +#ifdef CONFIG_KQEMU kqemu_init (env);#endif
After digging through the dependencies of apic and cpu again, this looks safe (it reorders reset execution, but that should have no side effect).
Jan
Signature · 2 lines
Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux
Re: [Qemu-devel] [PATCH 1/4] move registering of cpu_reset to inside cpu_init
In reply to Glauber CostaQuoted 7 lines · Glauber Costa
This is not pc specific by any means. So we can be
moved to insidecpu_x86_init().This is part of an attempt to only initialize kvm state after everything is already properly initialized. If we don't do that, we can race against, for example, APIC state if kvm vcpus are ran in threads (happens in qemu-kvm.git, soon to happen here too)
I'd move this too to exec.c. Sparc registers two reset functions, the first one for the main cpu disables halted state, the second one for non-boot cpus halts them on reset. I wonder why i386 does not do the same.
Re: [Qemu-devel] [PATCH 1/4] move registering of cpu_reset to inside cpu_init
Quoted 9 lines · Blue Swirl
Quoted 7 lines · Glauber Costa
This is not pc specific by any means. So we can be
moved to insidecpu_x86_init().This is part of an attempt to only initialize kvm state after everything is already properly initialized. If we don't do that, we can race against, for example, APIC state if kvm vcpus are ran in threads (happens in qemu-kvm.git, soon to happen here too)
Quoted 4 lines
I'd move this too to
exec.c. Sparc registers two reset functions, the first one for the main cpu disables halted state, the second one for non-boot cpus halts them on reset. I wonder why i386 does not do the same.
Probably because we were halting the cpu separatedly. Btw, after looking again, cpu_reset looks like an even better place to hold the halted change.