Richard Cochran wrote:
> > -Original Message- From: Gilles Chanteperdrix
> >> *IXP4XX_OSRT1 = LATCH | ONE_SHOT_ENABLE;
> >
> > In fact, should not this be:
> >
> > *IXP4XX_OSRT1 =
> > (last_jiffy_time + LATCH - *IXP4XX_OSTS) |
> ONE_SHO
Richard Cochran wrote:
> > -Original Message- From: Gilles Chanteperdrix
> >
> > For reasons explained on the wiki, I would rather see
> > ixp4xx_timer_interrupt implemented as:
> >
> >if (__ipipe_mach_timerstolen) {
> >/* If some other domain has taken over the tim
> -Original Message- From: Gilles Chanteperdrix
>
> The reason for not looping is that Adeos never looses interrupts. If
> we leave the loop and Linux gets delayed, then the lost ticks will
> be accounted for twice: one time because Xenomai will have posted
> the missed timer interrupts, o
Here is the corrected patch, based on Gilles' comments.
I hope sending this as an attachment is ok. I am a former Mutt user,
now forced to use **tl**k, and I can never tell when this program
wraps the lines...
Richard
Richard C
Krause, Karl-Heinz wrote:
> Hi Philippe
>
>
>
> as promised some time ago, I'd like to let you know the result of our work.
>
> Attached are
>
> - a few recycled slides from a presentation describing motivation,
> features and results
>
> - the patch file for a adeos-ipi
Hi Philippe,
here is an explanation of the scalable scheduler issue I face on x86_64
under different gcc compilers:
unsigned long x = 0;
int n = 32;
x |= 1 << n;
The last instruction translates to:
mov0xfffc(%rbp),%ecx
mov$0x1,%eax
Richard Cochran wrote:
> Here is the corrected patch, based on Gilles' comments.
>
> I hope sending this as an attachment is ok. I am a former Mutt user,
> now forced to use **tl**k, and I can never tell when this program
> wraps the lines...
This patch is Ok for me. Philippe, could you merg
On Wed, 2007-04-18 at 20:13 +0200, Jan Kiszka wrote:
> Hi Philippe,
>
> here is an explanation of the scalable scheduler issue I face on x86_64
> under different gcc compilers:
>
> unsigned long x = 0;
> int n = 32;
>
> x |= 1 << n;
>
> The last instruction translates to
On Wed, 2007-04-18 at 21:59 +0200, Gilles Chanteperdrix wrote:
> Richard Cochran wrote:
> > Here is the corrected patch, based on Gilles' comments.
> >
> > I hope sending this as an attachment is ok. I am a former Mutt user,
> > now forced to use **tl**k, and I can never tell when this program
Philippe Gerum wrote:
> - the posix registry
Is it enough to replace 1 << (fd % BITS_PER_LONG)
with 1L << (fd % BITS_PER_LONG) ?
--
Gilles Chanteperdrix.
___
Xenomai-core mailing list
Xenomai-core@gna.or
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > - the posix registry
>
> Is it enough to replace 1 << (fd % BITS_PER_LONG)
> with 1L << (fd % BITS_PER_LONG) ?
>
Yes, of course!
Jan
signature.asc
Description: OpenPGP digital signature
___
Philippe Gerum wrote:
> On Wed, 2007-04-18 at 20:13 +0200, Jan Kiszka wrote:
>> Hi Philippe,
>>
>> here is an explanation of the scalable scheduler issue I face on x86_64
>> under different gcc compilers:
>>
>> unsigned long x = 0;
>> int n = 32;
>>
>> x |= 1 << n;
>>
>> The
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Philippe Gerum wrote:
> > > - the posix registry
> >
> > Is it enough to replace 1 << (fd % BITS_PER_LONG)
> > with 1L << (fd % BITS_PER_LONG) ?
> >
>
> Yes, of course!
But ffs on x86_64 takes an int as argument, not a long. So, my
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> > > Philippe Gerum wrote:
> > > > - the posix registry
> > >
> > > Is it enough to replace 1 << (fd % BITS_PER_LONG)
> > > with 1L << (fd % BITS_PER_LONG) ?
> > >
> >
> > Yes, of course!
>
> But ffs on
Stelian Pop wrote:
> Hi,
>
> The attached patch adds an option to make Xenomai userspace issue EABI
> syscalls. This is needed to make Xenomai work with kernels compiled with
> CONFIG_EABI.
>
> Note that due to a change in syscall handling when the EABI layer was
> added in the kernel, th
Le jeudi 19 avril 2007 à 01:35 +0200, Gilles Chanteperdrix a écrit :
> Stelian Pop wrote:
> > Hi,
> >
> > The attached patch adds an option to make Xenomai userspace issue EABI
> > syscalls. This is needed to make Xenomai work with kernels compiled with
> > CONFIG_EABI.
> >
> I get a proble
16 matches
Mail list logo