diff --git a/sig/sig-ohos_kernel/.keep b/sig/sig-ohos_kernel/.keep new file mode 100644 index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 diff --git a/sig/sig-ohos_kernel/sig_kernel.md b/sig/sig-ohos_kernel/sig_kernel.md new file mode 100644 index 0000000000000000000000000000000000000000..b85e496b5781259be4a510fd2968ff49eaeba4bf --- /dev/null +++ b/sig/sig-ohos_kernel/sig_kernel.md @@ -0,0 +1,72 @@ +# Open Source Kernels in OpenHarmony OS + +[TOC] + +## 1. Summary + +Kernels are the SW abstraction that allow us to run applications on a broad range of HW. By themselves, kernels are not very interesting since they merely act on the behalf of applications to access HW resources. However, it is important that kernels are extremely resource efficient and secure so as to prevent hostile code from taking over HW. + +From the point of view of OpenHarmony, the goal is to ensure we support the best-in-class kernels required to run our applications as efficiently as possible to as many HW platforms as possible in a secure manner. + +### 1.1 Goals + +The role of this core group is to ensure that OpenHarmony supports the broadest range of CPUs, SoCs, peripherals and communication technologies - via buses or network - with open-source kernels. This SIG will work on identifying key technologies that need to be integrated into the kernels to provide a tightly integrated and performant HW abstraction to run OpenHarmony Services and applications on. + +### 1.2 Scope + +This group will have the following high-level goals: + +1. Continuously evaluate support for best-in-class kernels to address broadest possible SoC and peripheral support +1. Evaluate new kernels that might be proposed by partners for integration into OpenHarmony in terms of what value it brings to the Ecosystem +1. Work with other core groups and partners to identify key technologies that need kernel integration to enable new usecases and bring it into OpenHarmony +1. Work with the Application Framework teams to provide an abstraction layer for each technology that needs to be exposed to Application developers independent of the underlying kernel +1. Contribute to and influence upstream projects on technical issues with integrating upstream kernel components into solutions +1. Work with SoC and chipset vendors to provide support for their HW upstream and in OpenHarmony +1. Maintain a list of supported peripherals for each vertical solution to enhance cooperation and utilization within the OpenHarmony ecosystem + +### 1.3 Repository + +### 1.4 Non-Goals + +The following are not goals of this group: + +1. Writing new kernels: While the group will review proposals to include support for other kernels and other tightly integrated components such as network stacks, the main focus will be integration of the components on technical merit and value it brings to the ecosystem. Writing new kernels is not a goal. +1. Writing new drivers: The group will work with SoC and chipset vendors to integrate their drivers into OpenHarmony, not write them from scratch. + +### 1.5 Proposal + +The kernel core group will be responsible for maintaining the kernel support and architecture for OpenHarmony. Since the kernel talks to all the hardware, it is expected that this group will be involved in discussions in every part of the vertical solution stack e.g. multimedia, display subsystem, security, network technologies. + +The group will ensure that any external component being considered for integration into OpenHarmony that requires close integration with the kernel will work across all the supported kernels. + +#### 1.5.1 Story 1 + +OpenHarmony wants to add support for some network technology. The kernel core group will ensure that the exposed networking abstraction layer allows Linux and RTOS versions of the network technology to exist and work efficiently with the respective kernel network stacks. + +#### 1.5.2 Story 2 + +A partner wants to add support for a new RTOS to OpenHarmony. The kernel core group will evaluate the value this RTOS will bring to the ecosystem, the cost of porting the application layer to this new RTOS and supporting it inside OpenHamony. The group will decide on the what test suites are applicable for the new RTOS and monitor the results before support is added to OpenHarmony. + +#### 1.5.3 Story 3 + +Security team wants to introduce new techniques to secure OpenHarmony. The kernel core group will work with the security team to integrate these features as transparently as possible + +#### 1.5.4 Story 4 + +Upstream community needs help test and validate the stability of release candidates for the next LTS kernel. The kernel core group will help provide feeedback to upstream maintainers by the way our CI and test reports. + +#### 1.5.5 Story 5 + +Openharmony needs to decide on the supported kernel versions for the next release. This decision needs to take into account support for reference hardware from the partners, each kernel's LTS schedules and feature roadmaps. + +## 2. SIG Related information + +### 2.1 Maintainers +* Amit Kucheria [@idlethread] + +### 2.2 Mailing Lists +* would be nice to create a new ML for kernel. kernel@openharmony.io? + +### 2.3 Slack group +We use an Open Source alternative to Slack called Mattermost. +The kernel core group inside the OSTC Mattermost instance, hosted in EU, lives at [https://chat.ostc-eu.org/ostc/channels/kernel](https://chat.ostc-eu.org/ostc/channels/kernel).