This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: get interrupt stack
Hi,
I just want the eCos HAL and kernel (for scheduler part) and implement my own POSIX syscall.
(with cyg_hal_sys_kill mechanism I've done pthread_* , vfork, exec and kill in the synthetic target).
So even if it's a nested interrupt, a DSR or anything else, is it possible to get previous context
informations? (I've watched context.S it's very helpful, but I need a little more)
Thanks.
BR, jjp
----------------------------------------
> Date: Tue, 24 Jun 2008 16:02:01 +0200
> From: andrew@lunn.ch
> To: jackoaway@hotmail.com
> CC: gary@mlbassoc.com; ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] get interrupt stack
>
> On Tue, Jun 24, 2008 at 02:52:16PM +0100, trollepi jj wrote:
>>
>> Thanks for your quick reply.
>>
>> I try to implement a simple mecanism of signal on arm7 (I've done it with the synthetic target before -playing
>> with EBP and ESP - and it works well). I agree that an interrupt is anonymous but when a context switch happens
>> (clock interrupt). But where the informations of the current are stored in order to it gets back and continues its execution?
>> There is "obviously" a place in the thread stack or in an other structure to retrieve this information.
>
> Why are you assuming you are in thread context when the interrupt
> happens? It could be in nested interrupt. It could be in a DSR....
>
> Why not just use real signals as eCos implements?
>
> Andrew
_________________________________________________________________
Sur Windows Live Ideas, découvrez en exclusivité de nouveaux services en ligne... si nouveaux qu'ils ne sont pas encore sortis officiellement sur le marché !
http://ideas.live.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss