|To:||Franck Bui-Huu <firstname.lastname@example.org>|
|Subject:||Re: Question about signal syscalls !|
|From:||David Daney <email@example.com>|
|Date:||Fri, 02 Feb 2007 12:41:07 -0800|
|Cc:||Ralf Baechle <firstname.lastname@example.org>, linux-mips <email@example.com>|
|References:||<firstname.lastname@example.org> <20070201135734.GB12728@linux-mips.org> <email@example.com> <45C21CFE.firstname.lastname@example.org> <email@example.com> <45C3611D.firstname.lastname@example.org> <email@example.com> <45C36D46.firstname.lastname@example.org> <email@example.com>|
|User-agent:||Thunderbird 126.96.36.199 (X11/20061219)|
Franck Bui-Huu wrote:
On 2/2/07, David Daney <firstname.lastname@example.org> wrote:Franck Bui-Huu wrote: > David Daney wrote:>> The entire user context (i.e. the value of *all* registers) is replaced>> with the values stored in the sigcontext structure on the caller's >> stack. If all registers are being restored from the sigcontext, then >> there is no need to save the current values of the registers, because >> they will never be used. >> >Again, why do you think that all values of the registers are saved on sys_sigreturn() ?
I don't think that. I don't think I ever said that.
> And now I'm starting to think that we don't need to save static regs in > setup_sigcontext() either... > All registers *must* be saved in the sigcontext. That is part of the contract the kernel has with user code.I'm just talking about _static_ registers which are s0-s7...On return from an asynchronous signal, *all* registers must contain the same values they had before the process was interrupted.yes I agree and I've never said the contrary.
I thought you were suggesting not saving s0-s7. If you don't save them, you cannot restore them. And they have to be restored from the sigcontext in the user's address space. This allows user space signal handlers to emulate trapping instructions, and the like.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Question about signal syscalls !, Franck Bui-Huu|
|Next by Date:||[PATCH 1/1] APM-EMULATION: apm_get_power_status() should be NULL on init [was: Advice on battery support], Rodolfo Giometti|
|Previous by Thread:||Re: Question about signal syscalls !, Franck Bui-Huu|
|Next by Thread:||Re: Question about signal syscalls !, Daniel Jacobowitz|
|Indexes:||[Date] [Thread] [Top] [All Lists]|