From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: Huang Yi <linuxjoy@gmail.com>
Cc: <ecos-devel@sourceware.org>
Subject: Re: [ECOS] Miss calling ASR in sched.cxx
Date: Tue, 03 May 2011 06:38:00 -0000 [thread overview]
Message-ID: <4DBFA2E4.3040603@televic.com> (raw)
In-Reply-To: <BANLkTimH1C9E3O_zmRM17bSoEPuXUpNKtA@mail.gmail.com>
This is the correct list, but your attachment got lost.
Regards, Jürgen
On 05/03/2011 03:18 AM, Huang Yi wrote:
>
> 2011/4/22 kiron <linuxjoy@gmail.com>:
> > When enable both CYGSEM_KERNEL_SCHED_ASR_SUPPORT and
> > CYGIMP_KERNEL_INTERRUPTS_DSRS, consider that local variable call_asr
> > is set to true and clear the asr_pending flag of current thread, but
> > has DSRs_pending. It will continue the while loop and the call_asr's
> > value is re-initialized to false, code path will miss to call ASR.
> >
> > Posix timer use ASR to deliver signal,If missing to call ASR, and
> > signal will not been delivered. Unfortunately, posix time subsystem
> > don't try to reset the asr_pending flag (see alarm_action() in
> > packages/compat/posix/current/src/time.cxx), and the timer was
> > disarmed forever (If it is a interval timer).
> >
> > here is a small patch to fix this.
> >
> > Huang Yi
> > ------------------------
>
> Anybody can review this patch? or I should send the mail to another
> mail list?
>
> --
> Huang Yi (kiron)
> -------------------
>
--
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045 Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk
next prev parent reply other threads:[~2011-05-03 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 2:51 kiron
2011-05-03 1:18 ` Huang Yi
2011-05-03 6:38 ` Jürgen Lambrecht [this message]
2011-05-03 7:04 ` Huang Yi
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=4DBFA2E4.3040603@televic.com \
--to=j.lambrecht@televic.com \
--cc=ecos-devel@sourceware.org \
--cc=linuxjoy@gmail.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).