public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Arnaud Mouiche <arnaud.mouiche@inventel.fr>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] scheduler and clock question
Date: Fri, 20 Jul 2001 05:56:00 -0000	[thread overview]
Message-ID: <3B582A31.5EE82C0@redhat.com> (raw)
In-Reply-To: <5.0.2.1.0.20010720141217.00aa29a0@193.54.84.101>

Arnaud Mouiche wrote:
> 
> first, tell me if I'm right :
> 
> - the object 'Cyg_RealTimeClock' defined in the 'clock.cxx' files has an
> ISR. this ISR is called regulary (10 ms corresponding to the
> CYGNUM_KERNEL_COUNTERS_RTC_PERIOD value, generally equal to
> CYGNUM_HAL_RTC_PERIOD.)
> - to create this periodicaly call, it use 'hal_clock_initialize' and
> 'hal_clock_reset' specifics functions.
> - the ISR attachement is performed by the 'Cyg_RealTimeClock' constructor
> - every CYGNUM_KERNEL_SCHED_TIMESLICE_TICKS times an ISR rise for the timer
> (generally equal to 5), a call is made to the choosen scheduler object.
> this scheduler performs context switch and so..

Yes, all right. Although note it's the DSR (invoked after the ISR) that
does the work.
 
> Here my question :
> 
> There is no header defined for  'Cyg_RealTimeClock'  object. And there is
> no link with this object in any other files. In that case, who initializes
> this object (and so, who calls the contructor) ?

It's a static object, so once the file is linked in for any reason (which
it will be if the scheduler is used), then the constructor will be called
at system startup time.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

      reply	other threads:[~2001-07-20  5:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-20  5:30 Arnaud Mouiche
2001-07-20  5:56 ` Jonathan Larmour [this message]

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=3B582A31.5EE82C0@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=arnaud.mouiche@inventel.fr \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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).