postman
/
niobe
1
0
Fork 1
Code Issues Pull Requests Releases Wiki Activity
niobe/base/hiviewdfx/hiview_lite
History
houpengfei 396aa09915 init 2021-09-22 21:52:48 +08:00
..
.gitee init 2021-09-22 21:52:48 +08:00
blackbox init 2021-09-22 21:52:48 +08:00
hidumper_lite init 2021-09-22 21:52:48 +08:00
BUILD.gn init 2021-09-22 21:52:48 +08:00
LICENSE init 2021-09-22 21:52:48 +08:00
README.md init 2021-09-22 21:52:48 +08:00
README_zh.md init 2021-09-22 21:52:48 +08:00
hiview_cache.c init 2021-09-22 21:52:48 +08:00
hiview_cache.h init 2021-09-22 21:52:48 +08:00
hiview_config.c init 2021-09-22 21:52:48 +08:00
hiview_config.h init 2021-09-22 21:52:48 +08:00
hiview_def.h init 2021-09-22 21:52:48 +08:00
hiview_file.c init 2021-09-22 21:52:48 +08:00
hiview_file.h init 2021-09-22 21:52:48 +08:00
hiview_service.c init 2021-09-22 21:52:48 +08:00
hiview_service.h init 2021-09-22 21:52:48 +08:00
hiview_util.c init 2021-09-22 21:52:48 +08:00
hiview_util.h init 2021-09-22 21:52:48 +08:00

README.md

hiview Module

Overview

The hiview module provides the initialization of the DFX subsystem and controls the startup of each component as required.

Architecture

The DFX initialization consists of two phases: DEVICE_INIT and CORE_INIT.

DEVICE_INIT:

  1. The config component and core configuration parameters enabling or disabling the dump or event function of the DFX subsystem are initialized.

  2. The log component is initialized, without involving the dynamic memory allocation and file operation capabilities.

  3. The status information about the current DFX subsystem is written into the config component.

CORE_INIT:

  1. The log, dump, event, and output components are initialized as required based on the parameters of the config component.

  2. Memory management and file system operations are started normally. Memory can be requested and files can be created as required.

Repositories Involved

DFX subsystem

hiviwdfx_hilog_lite

hiviwdfx_hiview_lite

hiviwdfx_hievent_lite