SMP: ISR disable/enable vs. mutual exclustion

[Chris Johns]

Sebastian Huber wrote:
>
> To make them SMP ready we have two options.
>
> 1. Instead of ISR disable/enable use ISR locks. Advantage: not interface
> change. Disadvantage: space overhead for user which only use the
> unprotected routines.
>
> 2. Add a new chain API, e.g. new structure rtems_chain_with_lock which
> provides a chain + ISR lock. Advantage: you get what you need.
> Disadvantage: API duplication.
>

The space quoted is not large however I wonder if clearly stating the 
need for a locked chain in the code is an advantage in terms of readability.

We already have protected and unprotected now. Does this relate ?

> Subject: [PATCH] FIXME: Add and use _Assert_Owner_of_giant()

What is the FIXME referring to ?

Chris