Rename missed instances of nanoFiberStart()
Completes the renaming of nanoFiberStart() -> fiber_fiber_start(). There is little value in listing the callers of _NewContext() in its function header. Not only was the (deleted) list both incomplete and wrong, keeping it around and properly updated requires error prone maintenance. Change-Id: Ic45f51b285c027a2e8be331c0d28c16bdc97647d Signed-off-by: Peter Mitsis <peter.mitsis@windriver.com>
This commit is contained in:
parent
86ebbf406c
commit
19a0ee4d24
3 changed files with 4 additions and 4 deletions
|
@ -54,7 +54,7 @@ enabled or disabled at run-time:
|
|||
void task_float_disable (nano_context_id_t ctxId)
|
||||
|
||||
The 'options' parameter is used to specify what non-integer capabilities are
|
||||
being used. The same options accepted by nanoFiberStart() are used in the
|
||||
being used. The same options accepted by fiber_fiber_start() are used in the
|
||||
aforementioned APIs, namely USE_FP and USE_SSE.
|
||||
|
||||
If the VxMicro nanokernel has been built with support for automatic enabling
|
||||
|
|
|
@ -71,7 +71,7 @@ void _StartTaskArch(
|
|||
* both. The USE_SSE flag bit will only be set if a context uses SSE
|
||||
* instructions.
|
||||
*
|
||||
* However, callers of nanoFiberStart(), task_fiber_start(), or even
|
||||
* However, callers of fiber_fiber_start(), task_fiber_start(), or even
|
||||
* _NewContext() don't need to follow the protocol used by the IA-32
|
||||
* nanokernel w.r.t. managing the tCCS->flags field. If a context
|
||||
* will be utilizing just the x87 FPU capability, then the USE_FP
|
||||
|
|
|
@ -300,7 +300,7 @@ typedef void (*NANO_EOI_GET_FUNC) (void *);
|
|||
#define NANO_SOFT_IRQ ((unsigned int) (-1))
|
||||
|
||||
#ifdef CONFIG_FP_SHARING
|
||||
/* Definitions for the 'options' parameter to the nanoFiberStart() API */
|
||||
/* Definitions for the 'options' parameter to the fiber_fiber_start() API */
|
||||
|
||||
#define USE_FP 0x10 /* context uses floating point unit */
|
||||
#ifdef CONFIG_SSE
|
||||
|
@ -344,7 +344,7 @@ extern void irq_unlock(int key);
|
|||
/*
|
||||
* Dynamically enable/disable the capability of a context to share floating
|
||||
* point hardware resources. The same "floating point" options accepted by
|
||||
* nanoFiberStart() are accepted by these APIs (i.e. USE_FP and USE_SSE).
|
||||
* fiber_fiber_start() are accepted by these APIs (i.e. USE_FP and USE_SSE).
|
||||
*/
|
||||
|
||||
extern void fiber_float_enable(nano_context_id_t ctx, unsigned int options);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue