Gregory Nutt b4438e44c5 Restructuring of build to allow use of use-space allocators by kernel logic in the kernel build.

2014-09-02 11:22:09 -06:00

..

Make.defs

…

sched_addblocked.c

Tickless Stuff: Back out the risky timer operations when the ready-to-run list is modified. That is unsafe. An ugly workaround is just to keep an interval timer going all of the time with a minimum duration equal to the timeslice interval.

2014-08-12 11:12:00 -06:00

sched_addprioritized.c

…

sched_addreadytorun.c

Tickless Stuff: Back out the risky timer operations when the ready-to-run list is modified. That is unsafe. An ugly workaround is just to keep an interval timer going all of the time with a minimum duration equal to the timeslice interval.

2014-08-12 11:12:00 -06:00

sched_cpuload.c

…

sched_foreach.c

…

sched_free.c

Restructuring of build to allow use of use-space allocators by kernel logic in the kernel build.

2014-09-02 11:22:09 -06:00

sched_garbage.c

Rename kfree to kmm_free for consistency with other naming conventions

2014-08-31 17:04:02 -06:00

sched_getfiles.c

…

sched_getparam.c

…

sched_getscheduler.c

…

sched_getsockets.c

…

sched_getstreams.c

Rename CONFIG_NUTTX_KERNEL to CONFIG_BUILD_PROTECTED; Partially integrate new CONFIG_BUILD_KERNEL

2014-08-29 14:47:22 -06:00

sched_gettcb.c

…

sched_lock.c

…

sched_lockcount.c

…

sched_mergepending.c

…

sched_processtimer.c

…

sched_releasetcb.c

There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.

2014-09-01 15:39:34 -06:00

sched_removeblocked.c

…

sched_removereadytorun.c

Tickless Stuff: Back out the risky timer operations when the ready-to-run list is modified. That is unsafe. An ugly workaround is just to keep an interval timer going all of the time with a minimum duration equal to the timeslice interval.

2014-08-12 11:12:00 -06:00

sched_reprioritize.c

…

sched_rrgetinterval.c

…

sched_self.c

…

sched_setparam.c

nuttx/sched: Remove explicit references to errno. That is a problem from within the kernel for certain configurations

2014-08-28 17:00:24 -06:00

sched_setpriority.c

nuttx/sched: Remove explicit references to errno. That is a problem from within the kernel for certain configurations

2014-08-28 17:00:24 -06:00

sched_setscheduler.c

nuttx/sched: Remove explicit references to errno. That is a problem from within the kernel for certain configurations

2014-08-28 17:00:24 -06:00

sched_timerexpiration.c

Updated comments

2014-08-12 13:50:18 -06:00

sched_unlock.c

…

sched_verifytcb.c

…

sched_wait.c

…

sched_waitid.c

…

sched_waitpid.c

…

sched_yield.c

…

sched.h

Rename CONFIG_NUTTX_KERNEL to CONFIG_BUILD_PROTECTED; Partially integrate new CONFIG_BUILD_KERNEL

2014-08-29 14:47:22 -06:00