JavaScript promise rejection: Error: Loading CSS chunk katex failed. (http://111.8.36.180:3000/assets/css/katex.a42245c1.css). Open browser console to see more details.
Go to file
Guangyao Ma 5a80d4e1a3 fix: solve SIGCHLD ignored in sigsuspend()
在如下场景signal可能得不到及时处理:
1、进程A设置信号a阻塞
2、进程A收到信号a
3、进程A调用sigsuspend结束阻塞
原则上,步骤三应该立刻处理之前被阻塞的信号a,调用信号处理函数,并且sigsuspend
返回。现在的问题是,信号a没有得到及时处理,并且进程A阻塞在sigsuspend()调用流程
。
本次修改,在1、2、3场景下,sigsuspend()处理过程中,如果发现已经收到信号,待处理
时,会立刻进行调度切换,再次调度回来时,在调度模块中,会先主动处理已经收到的信
号,最后sigsuspend返回用户态。

close #I47CKK

Signed-off-by: Guangyao Ma <guangyao.ma@outlook.com>
Change-Id: I1b30a938a2d18c3f58989d40eee0503ceffb27b5
2021-08-26 15:36:13 +08:00
.gitee add issue and pr template 2021-04-07 14:49:32 +08:00
apps fix: avoid compile warning ignored 2021-06-15 19:56:21 +08:00
arch fix: Codex告警清零 2021-06-08 08:48:48 +08:00
bsd remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00
compat/posix 支持最小化特性编译,添加了一个针对qemu arm virt的样例config配置 2021-06-07 22:51:46 +08:00
drivers/char refactor: Refactored the kernel boot process and added a init framework 2021-05-20 16:45:43 +08:00
figures update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
fs fatfs支持symlink与readlink功能 2021-06-17 10:03:38 +08:00
kernel fix: solve SIGCHLD ignored in sigsuspend() 2021-08-26 15:36:13 +08:00
lib chore: build libc using third_party musl 2021-06-11 00:20:09 +08:00
net remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00
platform refactor: Refactored the kernel boot process and added a init framework 2021-05-20 16:45:43 +08:00
security remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00
shell refactor: Refactored the kernel boot process and added a init framework 2021-05-20 16:45:43 +08:00
syscall feat: support link/symlink/readlink 2021-06-09 16:39:41 +08:00
testsuites feat: support link/symlink/readlink 2021-06-09 16:39:41 +08:00
tools chore: build libc using third_party musl 2021-06-11 00:20:09 +08:00
.gitignore fix: Show conflicting files for git apply or patch -p command 2021-04-22 16:44:46 +08:00
BUILD.gn testsuites fixed 2021-04-30 15:07:26 +08:00
Kconfig fix(build): 去除冗余单板相关的宏配置 2021-06-09 14:02:52 +08:00
LICENSE update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
Makefile chore: add a mini config for qemu arm virt 2021-06-05 17:40:22 +08:00
README.md TicketNo:DTS2021012805GXU8P0H00 2021-03-16 16:54:09 +08:00
README_zh-HK.md add README_zh-HK.md. 2021-03-29 12:01:23 +08:00
README_zh.md README_zh.md: update the correct links 2021-06-03 09:24:50 +08:00
TODOList.md update TODOList.md. 2021-05-21 15:01:20 +08:00
build.sh fix: avoid compile warning ignored 2021-06-15 19:56:21 +08:00
config.mk remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00
kernel_test.sources remove __cplusplus guards in .c files 2021-04-19 18:28:25 +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. For more acquisition methods, see Source Code Acquisition.

Compilation and Building

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

Repositories Involved

Kernel subsystem

drivers_liteos

kernel_liteos_a