lnlan 26ee8b836e fix: 修复mqueue问题
【背景】
1.mqueue用例关于NFILE错误码压力测试中,不符合预期结果
2.mq_unlink对于fork出的mqueue不起效
3.已打开的mqueue,在fork后两进程共用一份mqpersonal不合理
【修改方案】
1. 确认是内核关于mqueue的fd_set定义位置不合理导致的,
将fd_set定义位置由mqarray结构体调未全局变量后,问题解决
2.不合理的unlink_ref++导致的,去除相关操作,使用mq_personal
链表判断何时需要删除
3.fork时内核复制一份mqpersonal
【影响】
对现有的产品编译不会有影响。

re #I43P4T

Signed-off-by: lanleinan <lanleinan@163.com>
Change-Id: I09f183cc3a88e5a65201dbc1fc4f4806f78971be
2021-08-10 07:55:13 +00:00
2021-04-07 14:49:32 +08:00
2021-07-22 01:50:19 +00:00
2021-08-10 07:55:13 +00:00
2021-03-11 18:43:57 +08:00
2021-08-10 07:55:13 +00:00
2021-07-30 17:13:55 +08:00
2021-07-21 15:52:40 +08:00
2021-03-11 18:43:57 +08:00
2021-03-16 16:54:09 +08:00
2021-05-21 15:01:20 +08:00

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

Description
No description provided
Readme 14 MiB
Languages
C 69.4%
C++ 27.9%
Makefile 1.8%
Assembly 0.7%
Shell 0.1%