Oopenvela-robotsched/atomic: fix the param defined but not use atomic API.
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
mm:support task heap Use MM_TASK_HEAP to control whether a task uses an internal task-specific heap. Use MM_TASK_HEAPSIZE to define the default heap size for each task. Additional APIs will be added later to assign a specific heap to a task Each task will allocate its own task heap from the user heap. The task heap is initialized when the task is initialized, and the task's stack is allocated from the task heap. The pthreads belonging to this task also use the task heap. This ensures isolation between task heaps. flat build and protect build can use task heap, heap view like this: |-kernal-|------------user heap----------------| |-task A heap--||-task B heap--|-free-| |-stack-|-heap-||-stack-|-heap-| Next: so if have mpu, We can change mpu region, when switch context, it can protect task heap Signed-off-by: anjiahao <anjiahao@xiaomi.com> | 2 个月前 | |
mm:support task heap Use MM_TASK_HEAP to control whether a task uses an internal task-specific heap. Use MM_TASK_HEAPSIZE to define the default heap size for each task. Additional APIs will be added later to assign a specific heap to a task Each task will allocate its own task heap from the user heap. The task heap is initialized when the task is initialized, and the task's stack is allocated from the task heap. The pthreads belonging to this task also use the task heap. This ensures isolation between task heaps. flat build and protect build can use task heap, heap view like this: |-kernal-|------------user heap----------------| |-task A heap--||-task B heap--|-free-| |-stack-|-heap-||-stack-|-heap-| Next: so if have mpu, We can change mpu region, when switch context, it can protect task heap Signed-off-by: anjiahao <anjiahao@xiaomi.com> | 2 个月前 | |
include/sched.h: remove implicit type conversions Coverity MISRA-CAST rejects implicit type conversions. Unified use of unsigned int type to modify FLAG. Signed-off-by: wangzhi16 <wangzhi16@xiaomi.com> | 2 个月前 | |
fix double unlock Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
fixtypo: fix the typo Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
nuttx/atomic: replace atomic_fetch_xxx with atomic_xxx just like zephyr Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com> | 2 个月前 | |
sched: rm group critical section Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
add group_delayfree, delay free task stack and tcb Signed-off-by: huojianchao<huojianchao@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
Protect:use MPU to protect elf_fixup apps global data Signed-off-by: anjiahao <anjiahao@xiaomi.com> | 2 个月前 | |
environ: move the environ from sched/environ to libc/environ change the environ implementation from sched/environ to libc/environ, thus we can access the environ related API can vai libc directl, which could improve the access speed in kernel build. And in order to support this modification, we change the struct task_info_s's ta_lock from nxmutex_t to nxrmutex_t, this is because the env_*-related APIs require the ta_lock to be reentrant. If recursive locks are not supported, it may lead to deadlocks in certain scenarios. For example, during initialization on the qemu-miwear platform, it is necessary to call getenv while already holding the ta_lock. To support such cases, we need to change the ta_lock from nxmutex_t to nxrmutex_t. Signed-off-by: guoshichao <guoshichao@xiaomi.com> | 2 个月前 | |
nuttx/atomic: replace atomic_fetch_xxx with atomic_xxx just like zephyr Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com> | 2 个月前 | |
sched/atomic: fix the param defined but not use atomic API. Cause if we try use the not-toolchain implement, try link to the toolchain version. Signed-off-by: buxiasen <buxiasen@xiaomi.com> | 2 个月前 | |
malloc: coverity HIS_metric_violation: RETURN Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
malloc: coverity HIS_metric_violation: RETURN Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
malloc: coverity HIS_metric_violation: RETURN Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
sched: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Signed-off-by: ligd <liguiding1@xiaomi.com> | 2 个月前 | |
group_setupidlefiles.c: coverity HIS_metric_violation: RETURN Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
sched/atomic: fix the param defined but not use atomic API. Cause if we try use the not-toolchain implement, try link to the toolchain version. Signed-off-by: buxiasen <buxiasen@xiaomi.com> | 2 个月前 | |
add support for CONFIG_DISABLE_SIGNALS 1. add the DISABLE_SIGNALS build option 2. make the sleep/usleep/nanosleep function can work with signal function disabled 3. make the driver/fs/sched/libc kernel module can decouple from signal module Signed-off-by: guoshichao <guoshichao@xiaomi.com> | 2 个月前 | |
sched: rm group critical section Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
mm:support task heap Use MM_TASK_HEAP to control whether a task uses an internal task-specific heap. Use MM_TASK_HEAPSIZE to define the default heap size for each task. Additional APIs will be added later to assign a specific heap to a task Each task will allocate its own task heap from the user heap. The task heap is initialized when the task is initialized, and the task's stack is allocated from the task heap. The pthreads belonging to this task also use the task heap. This ensures isolation between task heaps. flat build and protect build can use task heap, heap view like this: |-kernal-|------------user heap----------------| |-task A heap--||-task B heap--|-free-| |-stack-|-heap-||-stack-|-heap-| Next: so if have mpu, We can change mpu region, when switch context, it can protect task heap Signed-off-by: anjiahao <anjiahao@xiaomi.com> | 2 个月前 |