Go to file
LiteOS2021 dc9ec6856f feat: L0-L1 支持Trace
1.【需求描述】
            L0~L1 支持Trace,提供两种工作模式:在线模式、离线缓存模式, 用于按时间线追踪系统事件,如任务切换、中断、ipc等。
        2.【方案描述】
            L0:
            (1).在内核模块预置静态代码桩
            (2).触发桩后,收集系统上下文信息
            (3).离线模式则写入内存,用户可通过dump导出;
            (4).在线模式通过pipeline对接IDE进行可视化解析和展示;
            L1:
            新增trace字符设备,位于"/dev/trace",通过对设备节点的read\write\ioctl,实现用户态trace;

        BREAKING CHANGE:
        1.新增一系列trace的对外API,位于los_trace.h中.
        LOS_TRACE_EASY简易插桩
        LOS_TRACE标准插桩
        LOS_TraceInit配置Trace缓冲区的地址和大小
        LOS_TraceStart开启事件记录
        LOS_TraceStop停止事件记录
        LOS_TraceRecordDump输出Trace缓冲区数据
        LOS_TraceRecordGet获取Trace缓冲区的首地址
        LOS_TraceReset清除Trace缓冲区中的事件
        LOS_TraceEventMaskSet设置事件掩码,仅记录某些模块的事件
        LOS_TraceHwiFilterHookReg注册过滤特定中断号事件的钩子函数

        Close #I46WA0

    Signed-off-by: LiteOS2021 <dinglu@huawei.com>

Change-Id: I6a8e64794c4852f2c2980993a06180e09ec6ee0d
2021-08-31 20:29:45 +08:00
.gitee add issue and pr template 2021-04-07 14:49:32 +08:00
apps feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
arch feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
bsd chore(make): optimize build scripts 2021-08-30 17:18:21 +08:00
compat chore(musl): reduce the modifications of musl 2021-08-19 16:07:12 +08:00
drivers feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
figures update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
fs feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
kernel feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
lib chore(make): optimize build scripts 2021-08-30 17:18:21 +08:00
net chore: add default group automatly if needed 2021-08-06 12:05:56 +08:00
platform feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
security Merge branch 'master' of gitee.com:openharmony/kernel_liteos_a into misc 2021-07-27 01:40:59 +00:00
shell feat: add support for gn build system 2021-07-21 15:52:40 +08:00
syscall !570 fix ppoll & add 2 testcases 2021-08-30 02:06:24 +00:00
testsuites feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
tools feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
.gitignore chore(make): fix and optimize some build scripts 2021-08-23 20:47:18 +08:00
BUILD.gn chore: optimize build scripts and add lto config entry 2021-08-31 12:04:34 +08:00
Kconfig feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
LICENSE update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
Makefile chore: optimize build scripts and add lto config entry 2021-08-31 12:04:34 +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
TODOList.md update TODOList.md. 2021-05-21 15:01:20 +08:00
build.sh feat(make): optimize makefiles and remove some unused files 2021-08-22 04:23:40 +08:00
config.mk chore(make): optimize build scripts 2021-08-30 17:18:21 +08:00
liteos.gni chore: optimize build scripts and add lto config entry 2021-08-31 12:04:34 +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