From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] target width of shifts on 64 bits
Date: Mon, 23 Apr 2007 14:48:59 +0200 [thread overview]
Message-ID: <462CAB3B.9080408@domain.hid> (raw)
In-Reply-To: <17964.36864.695360.167360@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
> > Philippe Gerum wrote:
> > > On Mon, 2007-04-23 at 11:35 +0200, Jan Kiszka wrote:
> > > > BTW, with latest SVN trunk and scalable sched, the oopses are gone but
> > > > latency still doesn't start up:
> > > >
> > > > root@domain.hid :/root# cat /proc/xenomai/sched
> > > > CPU PID PRI PERIOD TIMEOUT TIMEBASE STAT NAME
> > > > 0 0 -1 0 0 master R ROOT
> > > > 0 930 0 0 0 master R display-928
> > > > 0 931 99 0 0 master R sampling-928
> > > > root@domain.hid :/root# cat /proc/xenomai/stat
> > > > CPU PID MSW CSW PF STAT %CPU NAME
> > > > 0 0 0 0 0 00500080 100.0 ROOT
> > > > 0 930 0 0 0 00300188 0.0 display-928
> > > > 0 931 0 0 0 00300188 0.0 sampling-928
> > >
> > > Two threads in ready state with higher priority than the root one: this
> > > means that a rescheduling opportunity has been missed, or more
> > > precisely, someone may be lying to xnpod_schedule() wrt to priority
> > > ordering when the scalable sched is enabled.
> >
> > ffsmlq uses ffnz, and there are two implementations of ffnz, one in
> > asm/hal.h which is correct on x86_64, the other in nucleus/system.h
> > which uses ffs hence only operates on ints.
>
> Never mind, nucleus/system.h is only included when using Xenomai headers
> in user-space. Nevertheless, it should probably use ffsl instead of ffs.
>
Who the hell is using the ffnz implementation in system.h? The
simulator? I kicked it out for a x64-build here, and I got no noticeable
effects.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-04-23 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 18:13 [Xenomai-core] [BUG] target width of shifts on 64 bits Jan Kiszka
2007-04-18 20:07 ` Philippe Gerum
2007-04-18 20:27 ` Gilles Chanteperdrix
2007-04-18 21:07 ` Jan Kiszka
2007-04-18 21:30 ` Gilles Chanteperdrix
2007-04-18 22:05 ` Jan Kiszka
2007-04-18 21:07 ` Jan Kiszka
2007-04-23 9:35 ` Jan Kiszka
2007-04-23 10:30 ` Philippe Gerum
2007-04-23 10:37 ` Gilles Chanteperdrix
2007-04-23 10:52 ` Gilles Chanteperdrix
2007-04-23 12:48 ` Jan Kiszka [this message]
2007-04-23 13:00 ` Gilles Chanteperdrix
2007-04-23 13:04 ` Jan Kiszka
2007-04-23 13:08 ` Philippe Gerum
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=462CAB3B.9080408@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.