From: e.coullien@faiveley.com
To: ecos-discuss@ecos.sourceware.org, ecos-patches@ecos.sourceware.org
Subject: [ECOS] eCos Interrupt timing
Date: Fri, 24 Jun 2005 12:59:00 -0000 [thread overview]
Message-ID: <C125702A.004751CA.00@smtp.faiveley.fr> (raw)
Hello,
We try to understand what ecos is doing when receiving an interrupt.
We modified temporally the file vector.S to trace on a logic output a signal
that represent how long is the interrupt time process
In this file, we set the signal before the context saving and we unset it just
before the context restoring
Then on the oscilloscope, we see that the signal is set at every tick system and
it is unset 500us (for a tick of 1ms) later.
During this time, The Decrementer ISR is executed (100 us) then interrupt_end().
It seems most of the time is spent in cyg_scheduler::unlock().
We don't understand what does ecos during these 400us (500-100).
Does somebody have an idea ?
Thanks,
Emmanuel Coullien
NOTE : CE COURRIER ELECTRONIQUE EST DESTINE EXCLUSIVEMENT AU(X) DESTINATAIRE(S) MENTIONNE(S) CI-DESSUS ET PEUT CONTENIR DES INFORMATIONS PRIVILEGIEES, CONFIDENTIELLES ET/OU ET/OU NON SOUMISES A DIVULGATION AUX TERMES DES LOIS APPLICABLES . SI VOUS AVEZ RECU CE MESSAGE PAR ERREUR , OU S'IL NE VOUS EST PAS DESTINE, VEUILLEZ LES SIGNALER IMMEDIATEMENT A L'EXPEDITEUR ET EFFACER CE COURRIER ELECTRONIQUE.
NOTE: This e-mail message is intended only for the named recipient(s) above and may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-06-24 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 12:59 e.coullien [this message]
2005-06-24 13:18 ` Andrew Lunn
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=C125702A.004751CA.00@smtp.faiveley.fr \
--to=e.coullien@faiveley.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ecos-patches@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).