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] Access to saved registers from Cortex-M ISR
Date: Fri, 07 Jan 2011 14:36:00 -0000	[thread overview]
Message-ID: <20110107143553.DFFCC2F7800B@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001111-13@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=1001111

--- Comment #2 from John Dallaway <john@dallaway.org.uk> 2011-01-07 14:35:52 GMT ---
Nick, thanks for your comments.

(In reply to comment #1)

> The intention with the code as it was written is that if anything needs access
> to the interrupt state then it should enable the existing code that saves a
> full and complete CPU state and stores it in hal_saved_interrupt_state; either
> by defining the CTRLC support option or by new means. Interested code can then
> fetch it from there. That way this code is only included when this
> functionality is required.

I looked at hal_saved_interrupt_state, but it is declared only when the GDB
break/Ctrl-C support is enabled. So...

> The extra ISR argument is also a bad idea, it has
> caused problems in other architectures and my intention was to keep the
> Cortex-M architecture clean and not have it.
> 
> There is maybe a case for defining a CDL option that controls this piece of
> code and have that depend on CTRLC and BREAK support, as well as allowing it
> to be enabled by any other package.

I would like to propose a CYGINT_HAL_COMMON_SAVED_INTERRUPT_STATE_REQUIRED CDL
interface which controls the declaration of 'hal_saved_interrupt_state'. The
interface would be implemented by all of the following:

 * CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
 * CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT
 * profiling CDL options within those HALs which make use of
      'hal_saved_interrupt_state' for profiling

Individual architecture HALs could then test for
CYGINT_HAL_COMMON_SAVED_INTERRUPT_STATE_REQUIRED > 0 to determine if it is
necessary to assign a value to 'hal_saved_interrupt_state'.

Other than the common HAL package, HAL packages would only require modification
if/when the use of 'hal_saved_interrupt_state' outside the context of GDB
Ctrl-C/break becomes necessary.

The advantage of a CDL interface over a CDL option in this context is that the
saved interrupt state support is automatically disabled when no-longer
required. eg When profiling was being used but is now disabled.

Again, any comments are welcome. I'll pick this up again next week.

-- 
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.


  parent reply	other threads:[~2011-01-07 14:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 11:29 [Bug 1001111] New: " bugzilla-daemon
2011-01-07 13:39 ` [Bug 1001111] " bugzilla-daemon
2011-01-07 14:36 ` bugzilla-daemon [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2011-01-07 11:29 [Bug 1001111] New: " bugzilla-daemon
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

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=20110107143553.DFFCC2F7800B@mail.ecoscentric.com \
    --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: 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).