Hi,
Il 19/06/23 19:53, Almudena Garcia ha scritto:
The cpus are started sequentially: don't start the next until the current has
finished its configuration.
in this case I think it's not needed to have a per-cpu bootstrap stack,
assuming the secondary cpu already runs a proper thread (i.e. K
Hi:
The cpus are started sequentially: don't start the next until the current has
finished its configuration.
But your idea is good
Thanks
El lunes 19 de junio de 2023, Luca Dariz escribió:
> Il 17/06/23 23:12, Samuel Thibault ha scritto:
> > Luca Dariz, le jeu. 15 juin 2023 23:49:30 +0200,
Il 17/06/23 23:12, Samuel Thibault ha scritto:
Luca Dariz, le jeu. 15 juin 2023 23:49:30 +0200, a ecrit:
diff --git a/i386/i386/ktss.c b/i386/i386/ktss.c
index 1d880167..52f3722c 100644
--- a/i386/i386/ktss.c
+++ b/i386/i386/ktss.c
@@ -61,6 +61,7 @@ ktss_fill(struct task_tss *myktss, struct real
Luca Dariz, le jeu. 15 juin 2023 23:49:30 +0200, a ecrit:
> diff --git a/i386/i386/ktss.c b/i386/i386/ktss.c
> index 1d880167..52f3722c 100644
> --- a/i386/i386/ktss.c
> +++ b/i386/i386/ktss.c
> @@ -61,6 +61,7 @@ ktss_fill(struct task_tss *myktss, struct real_descriptor
> *mygdt)
> /* Initia
* i386/i386/idt.c: add selector for the interrupt-specific stack
* i386/i386/ktss.c: configure ist1
* i386/i386/trap.c: add double fault handler, which just prints the
state and panics. There is not much else to do in this case but it's
useful for troubleshooting
* x86_64/idt_inittab.S: allow t
