Re: [PATCH 24/28] ddb/db_mp.c (remote_db): comment the call to cpu_interrupt_to_db()

[Samuel Thibault]

Marin Ramesa, le Sun 08 Dec 2013 12:40:26 +0100, a écrit :
> This wasn't noticed before since the number of cpus is always one I guess, but
> cpu_interrupt_to_db() is without definition. Comment the call.

Well, I prefer the issue to be noticed at compilation and thus spotted
immediately rather than by the stuff not working correctly, and the poor
hacker wondering why not...

> * ddb/db_mp.c (cpu_interrupt_to_db): Comment the call.
> 
> ---
>  ddb/db_mp.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/ddb/db_mp.c b/ddb/db_mp.c
> index b99718e..1b1277e 100644
> --- a/ddb/db_mp.c
> +++ b/ddb/db_mp.c
> @@ -152,7 +152,7 @@ remote_db() {
>               machine_slot[i].is_cpu &&
>               machine_slot[i].running)
>           {
> -             cpu_interrupt_to_db(i);
> +             /*cpu_interrupt_to_db(i);*/
>           }
>       }
>  }
> -- 
> 1.8.1.4
> 
> 

-- 
Samuel
<P> je sens venir la fonte 14 pour le rapport
 -+- #ens-mim -+-