From: michael trimarchi <trimarchi@gandalf.sssup.it>
To: root@chaos.analogic.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Real time
Date: Wed, 07 Jul 2004 12:00:06 +0200 [thread overview]
Message-ID: <40EBC9A6.1070400@gandalf.sssup.it> (raw)
In-Reply-To: <Pine.LNX.4.53.0407010650240.13048@chaos>
Richard B. Johnson wrote:
>On Thu, 1 Jul 2004, michael trimarchi wrote:
>
>
>
>>Hi,
>>I'm working on porting modular real time scheduler on linux layer ...
>>I'm using only kernel thread... Actually I dont't call the
>>kernel_thread(init, .... and I inizialize my scheduler and OS struct...
>>I schedule my kernel thread... I'm trying to use the printk in the
>>kernel_thread but sometimes I dont't having result on the console. The
>>console does't print my debug on screen... Is there an unburred printk?
>>
>>Best regards
>>Michael Trimarchi
>>
>>
>>
>
>You probably need to set up your kernel thread correctly. You should
>use:
> kernel_thread(your_thread, NULL, CLONE_FS|CLONE_FILES);
>
>your_thread(void *whatever)
>{
> exit_files(current);
> daemonize();
> /.../ fix up signals, etc.
>}
>
>Without CLONE_FILES, the file-descriptors and handles ultimately
>used for printk() may not work.
>
>Cheers,
>Dick Johnson
>Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
> Note 96.31% of all statistics are fiction.
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
Thank's,
now I schedule kernel thread width edf, rr, and other...
Best regards
Michael Trimarchi
prev parent reply other threads:[~2004-07-07 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 8:22 michael trimarchi
2004-07-01 10:57 ` Richard B. Johnson
2004-07-01 13:43 ` michael trimarchi
2004-07-07 10:00 ` michael trimarchi [this message]
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=40EBC9A6.1070400@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®