From: Jan Kiszka <jan.kiszka@domain.hid>
To: Steven Seeger <steve@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] no-brainer issue found, but not solved
Date: Wed, 22 Feb 2006 16:00:30 +0100 [thread overview]
Message-ID: <43FC7C8E.3040902@domain.hid> (raw)
In-Reply-To: <C021B37E.24C4%steve@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
Steven Seeger wrote:
> There is a awful amount of code in this project, and I should point out that
> this same code did not exhibit these problems under a fusion cvs from
You code contains a wrong assumption about the execution context. Older
Xenomai/fusion versions may have concealed this due to different
internal design.
> October. I can see about posting the full code, but my supervisors don¹t
> want anything having our hardware addresses in it going out.
>
> This is an x86 board, so inb/outb are just instructions.
Then please shrink down your scenario so that
a) no proprietary code or addresses are contained AND
b) only a minimum of surrounding code is used AND
c) the problem (timing issues) still show up.
This first of all means to replace the specific detection of deadline
misses (flickering LEDs) with a generic mechanism - e.g. the latency
tool. Then we can try to reproduce your problem or already find the
issue in the test code. As I pointed out: mixing non-RT with RT code is
feasible but requires careful design.
>
> I know about the volatile thing but that isn¹t my problem. I¹m having
> realtime preemption issues.
>
> Steven
>
> On 2/21/06 1:20 PM, "Jeroen Van den Keybus" <jeroen.vandenkeybus@domain.hid.com>
> wrote:
>
>> It would be helpful if a complete code could be posted. That means, including
>> the main() function, in which the task dispatching is done as well.
>>
>> Furthermore, be sure to declare counting variables inside waiting loops with
>> the 'volatile' specifier. The compiler might optimize it away otherwise.
>>
>> Another, maybe dumb suggestion: how is inb() / outb() actually implemented on
>> your platform ?
>>
>>
>> Jeroen.
>>
>>
>
>
>
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-02-22 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 17:38 [Xenomai-help] no-brainer issue found, but not solved Steven Seeger
2006-02-21 17:57 ` Jan Kiszka
2006-02-21 18:15 ` Steven Seeger
2006-02-21 18:36 ` Jan Kiszka
2006-02-21 21:20 ` Jeroen Van den Keybus
2006-02-22 14:21 ` Steven Seeger
2006-02-22 15:00 ` Jan Kiszka [this message]
2006-02-24 9:01 ` Philippe Gerum
2006-02-24 14:00 ` Steven Seeger
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=43FC7C8E.3040902@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=steve@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.