From: "Davy Wouters" <davy.wouters.atos@gmail.com>
To: ecos-devel@ecos.sourceware.org
Subject: New hal port + interrupts + rescheduling + call_pending_dsrs problem
Date: Fri, 27 Jun 2008 14:41:00 -0000 [thread overview]
Message-ID: <111ced750806270740k430d9ca9we3f3f1bd84d65ab7@mail.gmail.com> (raw)
Hi all,
I have done a hal port to the Analog Devices Blackfin processor
starting from the latest from cvs version of ecos.
I don't quite understand how the interrupt handling in
default_interrupt_vsr works.
When an interrupt occurs from my uart, i have a interrupt trampoline
which does some vector translation and then calls the
hal_interrupt_default_vsr which calls the isr of my uart rx interrupt.
This isr requests a dsr to run.
I have made the hal_interrupt_default_vsr as instructed ending with
the interrupt_end call from the interrupt object of the kernel.
One of the problems i seem to have is that call_pending_dsrs is called
(from within interrupt_end - scheduler::unlock_inner) while
the processor is still running at the interrupt level of my uart.
(Nested interrupts are disabled, no separate interrupt stack is used)
I assume a return from interrupt should be executed somewhere between
the execution of the isr/post_dsr and the call_pending_dsrs?
Where would this be done, in other words at which point in the hal do
i need to return from my interrupt?
Is it correct that call_pending_dsrs should be executed only when
other interrupts are allowed again, in other words after return from
the interrupt?
Sorry if my questions are a bit confusing, but i don't quite
understand the problems i'm having at this point (Crashes when having
a lot of communication
on my uart rx resulting in ASSERT_FAIL: <6>mutex.cxx[249]cyg_bool
Cyg_Mutex::lock() Locking mutex I already own)
Any suggestions?
Tnx,
Davy Wouters
Atos engineering
next reply other threads:[~2008-06-27 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 14:41 Davy Wouters [this message]
2008-06-27 18:25 ` Andrew Lunn
2008-06-30 8:27 ` Davy Wouters
2008-06-30 8:48 ` 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=111ced750806270740k430d9ca9we3f3f1bd84d65ab7@mail.gmail.com \
--to=davy.wouters.atos@gmail.com \
--cc=ecos-devel@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).