public inbox for
help / color / mirror / Atom feed
Subject: ecos/packages/kernel/current ChangeLog cdl/ker ...
Date: Tue, 01 Jul 2003 17:34:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	2003-07-01 17:34:54

Modified files:
	packages/kernel/current: ChangeLog 
	packages/kernel/current/cdl: kernel.cdl 
	packages/kernel/current/include: clock.hxx clock.inl 
	packages/kernel/current/src/common: clock.cxx 
Added files:
	packages/kernel/current/tests: kalarm0.c 

Log message:
	* include/clock.hxx: Made Cyg_Counter::add_alarm() and
	Cyg_Counter::rem_alarm() private functions. They no longer lock
	the scheduler, so should not be called directly, only via the
	Cyg_Alarm functions.
	* include/clock.inl: Removed inline version of
	Cyg_Alarm::disable(). It's no longer a one-liner and is thus
	better as a proper function.
	* src/common/clock.cxx (Cyg_Counter::tick): Rewrote the unsorted
	list option. If the function of one alarm adds or removes other
	alarms, then is was possible for the list to become corrupted. The
	new implementation attempts to avoid this problem.
	(Cyg_Alarm::initialize): Added scheduler locking to protect the
	enabled flag.
	(Cyg_Alarm::enable): Ditto.
	(Cyg_Alarm::disable): Ditto. Moved here from clock.inl.
	(Cyg_Alarm::add_alarm): Removed scheduler locking, it is now
	always called from functions that have already locked it. Added an
	assertion to double-check this.
	(Cyg_Alarm::rem_alarm): Ditto.
	* cdl/kernel.cdl:
	* tests/kalarm0.c:
	Added new test to test that alarms can be added and removed in
	alarm functions safely.

             reply	other threads:[~2003-07-01 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01 17:34 nickg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-09 18:06 vae
2007-01-08 16:20 nickg
2003-06-23 18:19 nickg
2003-01-31 11:44 nickg

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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