Fillod Stephane wrote:
> Hi!
>
> Why rt_timer functions, esp. rt_timer_tsc(), are not inlined in
> user-space
> (with CONFIG_XENO_HW_DIRECT_TSC) ? Is it because some policy insists
> that every library function must have an overridable symbol?
> Even a branch is worrisome when doing repetitive m
Hi!
Why rt_timer functions, esp. rt_timer_tsc(), are not inlined in
user-space
(with CONFIG_XENO_HW_DIRECT_TSC) ? Is it because some policy insists
that every library function must have an overridable symbol?
Even a branch is worrisome when doing repetitive micro-measurements.
What about a patch
Yasser Kashfi wrote:
> <5>119MB HIGHMEM available.
> <5>896MB LOWMEM available.
This kernel has still some highmem, so it was not compiled with
CONFIG_VMSPLIT_3G_OPT.
--
Gilles.
___
Xenomai-core mailing
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Gilles Chanteperdrix wrote:
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> OTOH, we can safe some text size which is precious as well. So I'm
>>> convinced to go your way (with a
Yasser Kashfi wrote:
> Hi everyone Thank Gilles for your reply. It's usefull for everyone to
> see kernel log befor system crash. you can see a port of
> /var/log/boot.msg and /var/log/message below:
And about CONFIG_VMSPLIT_3G_OPT ?
--
Gilles.
__
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> OTOH, we can safe some text size which is precious as well. So I'm
>> convinced to go your way (with a modification):
> My app
