Go to file
zhushengle 6d8cef40c8 feat: swtmr机制与调度分离,调度只针对通用线程,不针对特殊功能
背景:
原调度机制与软件定时器实现混合,调度时间链表存在两个链表,
任务切换时需要遍历两个链表才可以获取到最终的tick响应时间。
软件定时作为一个独立的功能,不应该和调度强耦合,而且软件定时
器作为一个任务,某个软件定时器的响应时间应该是软件定时器任务的
响应时间,不应该直接做为tick中断的响应时间。

方案描述:
1.将软件定时器从调度分离,作为一个独立的机制,从调度角度看其就是一个任务
2.软件定时器从调度分离之后,其timelist遍历从tick中断移动至软件定时器任务中
3.优化软件定时器的均衡调度

优势:
1.将软件定时器与调度完全分离,使得调度功能单一化,便于后续其它调度算法的引入
2.优化tick中断,减小tick中断耗时
3.优化通过写队列唤醒软件定时器任务去执行软件定时器钩子为插队列,减少软件定时
器机制本身的耗时,提升软件定时器的实时性
4.优化软件定时器均衡调度,使得软件定时器均匀分布于多核,提升软件定时器的实时性

Signed-off-by: zhushengle <zhushengle@huawei.com>
Change-Id: I07c01f134e69c1d9b7061ddf5a231df1ee99b68e
2022-03-19 11:23:36 +08:00
.gitee fix: pr模板补充说明 2022-01-21 17:17:21 +08:00
apps !829 fix:修改拼写错误 2022-03-14 10:45:10 +00:00
arch feat: swtmr机制与调度分离,调度只针对通用线程,不针对特殊功能 2022-03-19 11:23:36 +08:00
bsd refactor: 清理Makefile冗余项 2021-09-13 18:14:15 +08:00
compat fix:内源代码检视拼写错误修改 2022-03-14 17:34:46 +08:00
drivers fix:内源代码检视拼写错误修改 2022-03-14 17:34:46 +08:00
figures update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
fs fix:修复拼写错误 2022-03-14 22:22:56 +08:00
kernel feat: swtmr机制与调度分离,调度只针对通用线程,不针对特殊功能 2022-03-19 11:23:36 +08:00
lib feature: libc opt 2022-03-14 19:57:39 +08:00
net fix:修复拼写错误 2022-03-14 22:22:56 +08:00
platform refactor: 内核目录结构整理 2021-09-08 16:36:28 +08:00
security fix: 内源代码检视问题修改 2022-03-14 15:14:44 +08:00
shell !829 fix:修改拼写错误 2022-03-14 10:45:10 +00:00
syscall !829 fix:修改拼写错误 2022-03-14 10:45:10 +00:00
testsuites feat: swtmr机制与调度分离,调度只针对通用线程,不针对特殊功能 2022-03-19 11:23:36 +08:00
tools fix:内源代码检视拼写错误修改 2022-03-14 17:34:46 +08:00
.gitignore chore(make): fix and optimize some build scripts 2021-08-23 20:47:18 +08:00
BUILD.gn fix: 修复部分内核态测试用例 2022-03-16 17:16:55 +08:00
Kconfig fix:修复拼写错误 2022-03-14 22:22:56 +08:00
LICENSE update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
Makefile fix:修复拼写错误 2022-03-14 22:22:56 +08:00
OAT.xml fix: 内源代码检视问题修改 2022-03-14 15:14:44 +08:00
README.md fix: 修复3.1源码检视的问题 2022-03-09 09:34:31 +00:00
README_zh-HK.md fix: 修复3.1源码检视的问题 2022-03-09 09:34:31 +00:00
README_zh.md fix: 修复3.1源码检视的问题 2022-03-09 09:34:31 +00:00
build.sh chore(build): optimize build scripts, remove unused config files 2021-09-01 12:39:55 +08:00
bundle.json chore: kernel部件化 2022-01-24 16:18:32 +08:00
config.mk feat(build): support gcc toolchain 2021-12-05 02:49:48 +08:00
liteos.gni feat(build): support gcc toolchain 2021-12-05 02:49:48 +08:00

README.md

LiteOS Cortex-A

Introduction

The OpenHarmony LiteOS Cortex-A is a new-generation kernel developed based on the Huawei LiteOS kernel. Huawei LiteOS is a lightweight operating system OS built for the Internet of Things IoT field. With the rapid development of the IoT industry, OpenHarmony LiteOS Cortex-A brings small-sized, low-power, and high-performance experience and builds a unified and open ecosystem for developers. In addition, it provides rich kernel mechanisms, more comprehensive Portable Operating System Interface POSIX, and a unified driver framework, Hardware Driver Foundation HDF, which offers unified access for device developers and friendly development experience for application developers. Figure 1 shows the architecture of the OpenHarmony LiteOS Cortex-A kernel.

Figure 1 Architecture of the OpenHarmony LiteOS Cortex-A kernel

Directory Structure

/kernel/liteos_a
├── apps                   # User-space init and shell application programs
├── arch                   # System architecture, such as ARM
│   └── arm                # Code for ARM architecture
├── bsd                    # Code of the driver and adaptation layer module related to the FreeBSD, such as the USB module
├── compat                 # Kernel API compatibility
│   └── posix              # POSIX APIs
├── drivers                # Kernel drivers
│   └── char               # Character device
│       ├── mem            # Driver for accessing physical input/output (I/O) devices
│       ├── quickstart     # APIs for quick start of the system
│       ├── random         # Driver for random number generators
│       └── video          # Framework of the framebuffer driver
├── fs                     # File system module, which mainly derives from the NuttX open-source project
│   ├── fat                # FAT file system
│   ├── jffs2              # JFFS2 file system
│   ├── include            # Header files exposed externally
│   ├── nfs                # NFS file system
│   ├── proc               # proc file system
│   ├── ramfs              # RAMFS file system
│   └── vfs                # VFS layer
├── kernel                 # Kernel modules including the process, memory, and IPC modules
│   ├── base               # Basic kernel modules including the scheduling and memory modules
│   ├── common             # Common components used by the kernel
│   ├── extended           # Extended kernel modules including the dynamic loading, vDSO, and LiteIPC modules
│   ├── include            # Header files exposed externally
│   └── user               # Init process loading
├── lib                    # Kernel library
├── net                    # Network module, which mainly derives from the lwIP open-source project
├── platform               # Code for supporting different systems on a chip (SOCs), such as Hi3516D V300
│   ├── hw                 # Logic code related to clocks and interrupts
│   ├── include            # Header files exposed externally
│   └── uart               # Logic code related to the serial port
├── platform               # Code for supporting different systems on a chip (SOCs), such as Hi3516D V300
├── security               # Code related to security features, including process permission management and virtual ID mapping management
├── syscall                # System calling
└── tools                  # Building tools as well as related configuration and code

Constraints

  • Programming languages: C and C++
  • Applicable development boards: Hi3518E V300 and Hi3516D V300
  • Hi3518E V300 uses the JFFS2 file system by default, and Hi3516D V300 uses the FAT file system by default.

Usage

OpenHarmony LiteOS Cortex-A supports the Hi3518E V300 and Hi3516D V300. You can develop and run your applications based on both development boards.

Preparations

You need to set up the compilation environment on Linux.

Source Code Acquisition

Download and decompress a set of source code on a Linux server to acquire the source code.

Compilation and Building

For details about how to develop the first application, see:

Repositories Involved

Kernel subsystem

drivers_liteos

kernel_liteos_a