Real time

Real time

[michael trimarchi]

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

Re: Real time

[Richard B. Johnson]

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.

Re: Real time

[michael trimarchi]

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/
>
>  
>
I use CLONE_KERNEL but in my body I dont't call exit_files and
demonize... I change the linux scheduler width my scheduler and I use
only the switch_to  for context_switch from a task to another... I have
a task descriptor with a pointer to the task_t * ... At this time I have
a linux task_t struct and my personal task struct...

Best regards
Michael

Re: Real time

[michael trimarchi]

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