public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Erik Christiansen <erik@dd.nec.com.au>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Disabling interrupts when locking the scheduler
Date: Fri, 03 Jun 2005 08:48:00 -0000	[thread overview]
Message-ID: <20050603084643.GC716@dd.nec.com.au> (raw)

The possibility of disabling interrupts when locking the scheduler seems
built into the calling sequence:

Cyg_Scheduler::lock()            <-- Generates no code, anywhere. *1
   inc_sched_lock()
      HAL_SMP_SCHEDLOCK_INC
         HAL_DISABLE_INTERRUPTS  <-- Disables interrupts, if invoked.

While ref/kernel-interrupts.html confirms that interrupts are normally not
disabled, for improved interrupt latency, the code is there, if I can just
figure out how to turn it on. It's not conditionals, but seems to be
inheritance which causes Cyg_Scheduler::lock() to be excluded.

Has anyone tried this before?

(I'd prefer to enable the latent code, rather than just poke a
HAL_DISABLE_INTERRUPTS in front of Cyg_Scheduler::lock() in 66
places, and repeat for enabling.)

*1) No timeslicing, CYGSEM_HAL_USE_ROM_MONITOR == 1.

Erik



-- 
 _,-_|\    Erik Christiansen                    Phone: +61 3 9264 3416
/      \   Research & Development Division        Fax: +61 3 9264 3438
\_,-.__/   Voice Products Department
      v    NEC Business Solutions Pty. Ltd.     www.necbs.com.au

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2005-06-03  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03  8:48 Erik Christiansen [this message]
2005-06-03  9:37 ` Nick Garnett
2005-06-06  8:50   ` Erik Christiansen

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=20050603084643.GC716@dd.nec.com.au \
    --to=erik@dd.nec.com.au \
    --cc=ecos-discuss@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).