public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: backlog@bugs.ecos.sourceware.org Subject: [Bug 1000660] ARM HAL breaks on spurious interrupt Date: Wed, 23 Feb 2011 15:39:00 -0000 [thread overview] Message-ID: <20110223153925.D7F482F78004@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1000660-776@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000660 Morten Lave <ml@tctechnologies.tc> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ml@tctechnologies.tc --- Comment #4 from Morten Lave <ml@tctechnologies.tc> 2011-02-23 15:39:22 GMT --- I have seen the same problem and it is in both eCos 2.x and 3.0. We have created a fix which has worked well for 2.x and this as far as i can see works for 3.0 as well. The fix seems to be along the same lines as what has allegedly been done in eCosPro. We have replaced: // The return value from the handler (in r0) will indicate whether a // DSR is to be posted. Pass this together with a pointer to the // interrupt object we have just used to the interrupt tidy up routine. // don't run this for spurious interrupts! cmp v1,#CYGNUM_HAL_INTERRUPT_NONE beq 17f ldr r1,.hal_interrupt_objects With // The return value from the handler (in r0) will indicate whether a // DSR is to be posted. Pass this together with a pointer to the // interrupt object we have just used to the interrupt tidy up routine. // don't run this for spurious interrupts! cmp v1,#CYGNUM_HAL_INTERRUPT_NONE //ML23-02-2011, even spurious interrupts must unlock scheduler moveq r0,#0 ldr r1,.hal_interrupt_objects This will make sure that interrupt_end is called even for a spurious interrupt but no DSR is posted as r0 is zero and therefore the vector is ignored. This fix replaces a conditional branch with a conditional move so it would not add any latency to regular interrupt processing. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next parent reply other threads:[~2011-02-23 15:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-1000660-776@http.bugs.ecos.sourceware.org/> 2011-02-23 15:39 ` bugzilla-daemon [this message] 2008-12-11 22:19 [Bug 1000660] New: " bugzilla-daemon 2011-02-23 15:39 ` [Bug 1000660] " bugzilla-daemon
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=20110223153925.D7F482F78004@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=backlog@bugs.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: linkBe 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).