Re: [Xenomai-core] posix: only use rt_printf when in primary mode

2011-06-28 Thread Jan Kiszka
Hi Gilles,

dynamic printf backend selection is a suboptimal idea when you want
chronological output (not that uncommon during debugging). The native
printf may actually hit the screen (or the log file) before some earlier
queued rt_printf message because the dump thread is busy or has a lower
priority.

It's ok to do native printf for non-shadows. But once a thread was
mapped, printf needs to go through the rt queue, even in secondary mode.

Jan



signature.asc
Description: OpenPGP digital signature
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core


Re: [Xenomai-core] posix: only use rt_printf when in primary mode

2011-06-28 Thread Jan Kiszka
On 2011-06-28 22:48, Jan Kiszka wrote:
 Hi Gilles,
 
 dynamic printf backend selection is a suboptimal idea when you want
 chronological output (not that uncommon during debugging). The native
 printf may actually hit the screen (or the log file) before some earlier
 queued rt_printf message because the dump thread is busy or has a lower
 priority.

Oh, I missed the buffer flush - that should work.

Sorry for the noise.

Jan



signature.asc
Description: OpenPGP digital signature
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core


Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Allow drop_u_mode syscall from any context

2011-06-28 Thread Gilles Chanteperdrix
On 06/28/2011 11:01 PM, GIT version control wrote:
 Module: xenomai-jki
 Branch: for-upstream
 Commit: 5597470d84584846875e8a35309e6302c768addf
 URL:
 http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=5597470d84584846875e8a35309e6302c768addf
 
 Author: Jan Kiszka jan.kis...@siemens.com
 Date:   Tue Jun 28 22:10:07 2011 +0200
 
 nucleus: Allow drop_u_mode syscall from any context
 
 xnshadow_sys_drop_u_mode already checks if the caller is a shadow. It
 does that without issuing a warning message if the check fails - in
 contrast to do_hisyscall_event. As user space may call this cleanup
 service even for non-shadow threads (e.g. after shadow creation failed),
 we better silence this warning.
 
 Signed-off-by: Jan Kiszka jan.kis...@siemens.com

Jan,

I have a branch here, which allocates u_mode in the shared heap, so,
this syscall is about to become unnecessary.

See:
http://git.xenomai.org/?p=xenomai-gch.git;a=shortlog;h=refs/heads/u_mode

-- 
Gilles.

___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core