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

Rep:Re: [f-cpu] SR security



-----Message d'origine-----
De: cedric <cedric.bail@free.fr>
A: f-cpu@seul.org
Date: 07/08/02
Objet: Re: [f-cpu] SR security

<snip>
>  What I think we need to add :
>   - READ_ONLY, that say if we must trap or not when we access
> to read only SR
>   - WRITE_ONLY, idem but for read/write SR
>   - ASI, the Identifier of the current task
>   - IRQ_STACK_BASE and IRQ_STACK_SIZE, for being able to handle
> multiple IRQ at the same time
>   - TRAP_STACK_BASE and TRAP_STACK_SIZE, in case of multiple TRAP
> (I think it's not usefull, because the trap handler must do his job
> correctly)

 I forget some of them :
  - RANDOM, random key for pseudo-random initialisation (depend on the 
implementation)
  - USER, currently only the LSB is usefull to say if we are SUPER_USER
or 
not.

>>> A task should not know if it run in superuser mode or not. So ?

>>>Maybe we should add a free running timer, and "some" timer alarm that
generate interrupt (for complexe schuling policy, very precise timing,
low power,...).
nicO

Cedric
  
*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/

 
______________________________________________________________________________
Nouveau sur i (france), ne vous faites pas piquer votre nom!
Réservez dès à présent votre nom de domaine pour 1 Euro* HT/mois (*à partir de) 
http://www.ifrance.com/_reloc/signdom

*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/