bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH gnumach] kern/processor: Do not set default_pset.empty on boo


From: Samuel Thibault
Subject: Re: [PATCH gnumach] kern/processor: Do not set default_pset.empty on bootstrap
Date: Fri, 23 Feb 2024 13:59:58 +0100
User-agent: NeoMutt/20170609 (1.8.3)

Applied, thanks!

Damien Zammit, le ven. 23 févr. 2024 08:04:13 +0000, a ecrit:
> This is not needed because cpu_up does this when it comes online,
> it calls pset_add_processor().
> ---
>  kern/processor.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/kern/processor.c b/kern/processor.c
> index 33733a59..0e42fa37 100644
> --- a/kern/processor.c
> +++ b/kern/processor.c
> @@ -76,7 +76,6 @@ void pset_sys_bootstrap(void)
>       int     i;
>  
>       pset_init(&default_pset);
> -     default_pset.empty = FALSE;
>       for (i = 0; i < NCPUS; i++) {
>               /*
>                *      Initialize processor data structures.
> @@ -90,7 +89,6 @@ void pset_sys_bootstrap(void)
>       queue_enter(&all_psets, &default_pset, processor_set_t, all_psets);
>       all_psets_count = 1;
>       default_pset.active = TRUE;
> -     default_pset.empty = FALSE;
>  
>       /*
>        *      Note: the default_pset has a max_priority of BASEPRI_USER.
> -- 
> 2.43.0
> 
> 
> 

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]