Linux Kernel Summit discussions
 help / color / mirror / Atom feed

From: Tiejun Chen <tiejunc@vmware.com>
To: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] [TECH TOPIC] A Safety-critical Linux system architecture
Date: Wed, 12 Sep 2018 01:18:24 +0000	[thread overview]
Message-ID: <BY1PR0501MB14623C8F42765E4852FD5A39C51B0@BY1PR0501MB1462.namprd05.prod.outlook.com> (raw)

Linux is playing very well in the case of embedded system. And there is no doubt that IoT, internet of things, grows as larger. Actually a variety of embedded systems make IoT so Linux definitely still can contribute to IoT. The thing here is many IoT systems are deployed in the critical infrastructures like the energy generation, oil and gas center, avionic, automotive, etc, where software contexts need to be certified according to different specifications like ARINC 653, Automotive Safety Integrity Level, and so on. So we need to explore making Linux itself certified.

Some efforts like SIL2LinuxMP, which "aims at the certification of the base components of an embedded GNU/Linux RTOS running on a single-core or multi-core industrial COTS computer board. Base components are boot loader, root filesystem, Linux kernel and C library bindings to access the Linux kernel. With the exception of a minimal set of utilities to inspect the system, manage files and start test procedures, user space applications are not included." But looks now it's still at the early stage and not good enough in the production environment.

So could we discuss together if-how we build a safety-critical Linux system architecture? Here are some potential technologies:

Minimal kernel part with some light weight stacks.
Every system and user service are containerized, and even with hardware assisted technologies like SGX.
It's based on Unikernel concept.
One process or even one thread is restricted right there.
It might be having system audit with hypervisor.
How to verify Linux in such a safety-critical environment

But not limited these factors in terms of our safety-critical Linux system architecture.

Thanks
Tiejun

next             reply	other threads:[~2018-09-12  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  1:18 Tiejun Chen [this message]
2018-09-12 10:35 ` [Ksummit-discuss] [TECH TOPIC] A Safety-critical Linux system architecture Linus Walleij
2018-09-12 16:29   ` Darren Hart
2018-09-13  3:13     ` Tiejun Chen
2018-09-13  7:57       ` Linus Walleij
2018-09-13  9:50       ` Greg KH
2018-09-16 11:30         ` Tiejun Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BY1PR0501MB14623C8F42765E4852FD5A39C51B0@BY1PR0501MB1462.namprd05.prod.outlook.com \
    --to=tiejunc@vmware.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).