public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001111] New: Access to saved registers from Cortex-M ISR Date: Fri, 07 Jan 2011 11:29:00 -0000 [thread overview] Message-ID: <bug-1001111-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001111 Summary: Access to saved registers from Cortex-M ISR Product: eCos Version: CVS Platform: All OS/Version: Cortex-M Status: NEW Severity: enhancement Priority: normal Component: HAL AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: john@dallaway.org.uk CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Created an attachment (id=1072) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1072) cortexm-intr-state-110107.patch There is currently no access to the saved interrupt state from an ISR on Cortex-M. This is required for implementing profiling support and is commonly provided by passing a HAL_SavedRegisters* parameter into the ISR (eg ARM, PowerPC). On Cortex-M, interrupts are delivered via the C function hal_deliver_interrupt() which is called from the default interrupt VSR. The attached patch modifies the VSR to pass the interrupt state to hal_deliver_interrupt() unconditionally. hal_deliver_interrupt() then passes this parameter on to the ISR. API impact is confined to code which calls hal_deliver_interrupt() directly - currently a single instance in an STM32 springboard ISR only. The patch adds two machine code instructions to an unoptimised build of hal_deliver_interrupt(). The patch adds three machine code instructions to the default interrupt VSR in the case where GDB break support is not enabled. These three instructions could be made conditional on CYGPKG_PROFILE_GPROF, but access to the saved interrupt state is unconditional on other architectures. Comments? -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-01-07 11:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-07 11:29 bugzilla-daemon [this message] 2011-01-07 13:39 ` [Bug 1001111] " bugzilla-daemon 2011-01-07 14:36 ` bugzilla-daemon 2011-01-10 12:11 ` bugzilla-daemon 2011-01-10 14:28 ` bugzilla-daemon 2011-01-10 14:28 ` bugzilla-daemon 2011-01-13 11:47 ` bugzilla-daemon 2011-01-13 17:36 ` bugzilla-daemon 2011-01-13 18:01 ` bugzilla-daemon 2011-01-13 18:42 ` bugzilla-daemon 2011-01-07 11:29 [Bug 1001111] New: " 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=bug-1001111-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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).