Go to file
Haryslee 6c2b163c7d fix: 修复重复执行内存用例导致系统卡死问题
背景:重复执行内存测试用例约几百次,系统大概率出现卡死现象,经分析知,系统卡在
内存spinlock锁中,CPU1在获取内存spinlock锁后打印异常信息,此时循环buffer满了,
CPU0此时进入异常且尝试拿取内存spinlock锁,两个核都处于锁中断锁任务状态,CPU1
写事件触发调度打印输出失败,进而在write接口中死循环无法退出,导致两个核都卡住。
方案:在write接口中增加一个判断条件:当前核处于锁任务状态且循环buffer满了时候,
直接退出循环,丢弃打印信息(持有spinlock锁后一般禁止输出打印信息)。

close #I4F7PO

Signed-off-by: Haryslee <lihao189@huawei.com>
Change-Id: I3f49a1bb211821e9c5d1d220d6867962d6a45a79
2021-12-29 14:27:43 +08:00
.gitee add issue and pr template 2021-04-07 14:49:32 +08:00
apps feat(build): support gcc toolchain 2021-12-05 02:49:48 +08:00
arch !738 fix: 修复xts权限用例压测异常问题 2021-12-25 02:10:18 +00:00
bsd refactor: 清理Makefile冗余项 2021-09-13 18:14:15 +08:00
compat fix: A核代码静态告警定期清理 2021-11-15 02:47:08 +00:00
drivers !731 【请求检视】fix: 修复LOSCFG_FS_FAT_CACHE宏关闭后编译失败的BUG 2021-12-13 10:03:58 +00:00
figures update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
fs fix: change default permission of procfs to 0550 2021-12-24 12:03:58 +08:00
kernel fix: 修复重复执行内存用例导致系统卡死问题 2021-12-29 14:27:43 +08:00
lib refactor: los_cir_buf.c中接口整合 2021-12-14 11:00:36 +08:00
net chore: 修复社区反馈问题Percpu结构体注释错误 2021-11-10 10:20:33 +08:00
platform refactor: 内核目录结构整理 2021-09-08 16:36:28 +08:00
security refactor: 清理Makefile冗余项 2021-09-13 18:14:15 +08:00
shell !703 fix: 解决dmesg -s参数double lock问题 2021-12-08 10:56:48 +00:00
syscall !709 A核代码静态告警定期清理 2021-11-16 06:47:22 +00:00
testsuites !710 清理YES/NO宏 2021-11-18 09:32:42 +00:00
tools feat(build): support gcc toolchain 2021-12-05 02:49:48 +08:00
.gitignore chore(make): fix and optimize some build scripts 2021-08-23 20:47:18 +08:00
BUILD.gn fix: 编译框架在做编译入口的统一 2021-12-14 13:19:31 +00:00
Kconfig refactor: 内核目录结构整理 2021-09-08 16:36:28 +08:00
LICENSE update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
Makefile feat(build): support gcc toolchain 2021-12-05 02:49:48 +08:00
OAT.xml chore(oat): 删除二进制文件,并且新增oat屏蔽 2021-08-06 01:41:09 +08:00
README.md fix: 修复文档链接失效问题 2021-08-12 14:21:35 +08:00
README_zh-HK.md fix: 修复文档链接失效问题 2021-08-12 14:21:35 +08:00
README_zh.md fix: 修复文档链接失效问题 2021-08-12 14:21:35 +08:00
build.sh chore(build): optimize build scripts, remove unused config files 2021-09-01 12:39:55 +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