06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

pSOS+ <strong>System</strong> <strong>Calls</strong> t_create<br />

ARM<br />

Supervisor Stack Size<br />

Supervisor stack size is processor-dependent.<br />

PPC<br />

ARM<br />

960<br />

x86<br />

On ARM processors, a task can execute in either user mode or supervisor<br />

mode. A user stack is not needed if the task never executes in the user<br />

mode, in which case ustack is set to 0. If the task starts in the user<br />

mode, then ustack must be greater than 80 bytes to accommodate the<br />

requirements of the interrupt handler. The supervisor/user mode is set in<br />

the t_start() system call.<br />

On PowerPC and ARM processors, the stack size should be no less than<br />

512 bytes.<br />

On 960 processors, the stack size should be no less than 256 bytes.<br />

On x86 processors, the stack size should be no less than 128 bytes.<br />

Using the T_FPU Flag<br />

If the T_FPU flag is set, the size of the task's stack segment is extended to save and<br />

restore FPU registers. It should be set if the task uses the FPU. The extension added<br />

varies according to the processor being used.<br />

68K<br />

CF<br />

PPC<br />

On 68K processors, the stack is extended by 328 bytes.<br />

On ColdFire processors, there is no support for FPU. Hence this feature<br />

is not supported in pSOS+.<br />

On PowerPC processors, the stack is extended by 264 bytes.<br />

<strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong> 1-135<br />

1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!