public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre-Marie Boyer" <pm.boyer@orange.fr>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] data access fron an interrupt handler
Date: Sat, 16 Jul 2011 10:27:00 -0000	[thread overview]
Message-ID: <FF51E95B015C4CC1A28D2F9DADEE469D@sonybiranques> (raw)

Hi,

I plane to work with eCos : Install eCos kernel on a card with a LPC2106 uC
from a PC linux station, and make some tests.

But before this, I would like to know how interrupts handlers work exactly
in case of multitasking software :

 

My problem is about the globals variables access from within an interrupt
function of a particular task.

So, if the system work with several tasks. If in a task we have installed an
interrupt handler (ex:harware interrupt).

When the software is running, if this interrupt is launched by the hardware
while another task is running, what happen if in this interrupt we want
accessing (read or write) a global data of his task while this is not the
same task suspended by the interrupt ? 

Because in this case the task context is not the same, and I think that no
changing context is performed by the OS before running the interrupt.

I think this can be a problem when we are in virtual memory system (uC with
MMU ).

Could you give me some information? 

(I know this is not a specific question of eCos, but I have not found were
to ask this question. sory, and thank you in advance)
 



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2011-07-16 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 10:27 Pierre-Marie Boyer [this message]
2011-07-16 18:21 ` Stanislav Meduna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FF51E95B015C4CC1A28D2F9DADEE469D@sonybiranques \
    --to=pm.boyer@orange.fr \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).