ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ksummit-discuss@lists.linuxfoundation.org,
	Darren Hart <dvhart@infradead.org>
Cc: Nicholas Mc Guire <der.herr@hofr.at>,
	Jason Cooper <jason@lakedaemon.net>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Linux and Functional Safety
Date: Fri, 29 Jul 2016 22:48:24 +0200	[thread overview]
Message-ID: <39739692.jqz6N0cLYc@vostro.rjw.lan> (raw)
In-Reply-To: <20160729202500.GD3062@f23x64.localdomain>

On Friday, July 29, 2016 01:25:00 PM Darren Hart wrote:
> We are seeing a surge in demand for using Linux in safety critical systems, from
> a broad spectrum reaching from automotive and industrial automation to rail and
> aerospace.
> 
> Functional Safety is about risk management. It involves identification of
> hazards to systems which may impact the proper operation of a safety function
> and minimizing those risks. It is a complex end-to-end systematic process
> embodied in industry standards, principally IEC 61508 Ed 2 as well as derivative
> domain specific standards, such as ISO 26262 (Passenger vehicles below 3.5
> Tons).
> 
> These standards were developed to support purpose built MCU class hardware and
> very small software stacks (3 orders of magnitude smaller than the Linux
> kernel). Applying them to modern general purpose computer systems and operating
> systems is not straight forward. It requires a thorough mapping of processes and
> development of a convincing set of claims, argumentation, and evidence to
> certify these elements to the required safety integrity levels (discrete levels
> describing the overall risk reduction capabilities of a system).
> 
> The OSADL SIL2LinuxMP project has been working at developing these mappings and
> a body of evidence into a generic compliance route, conforming to IEC 61508
> Ed 2. The approach is largely dependent on the rigorous development model of key
> software stack elements, most notably glibc and the Linux kernel.  Git provides
> traceability for all changes and ample meta-data to apply statistical models to
> determine the quality and risk associated with each change. The static analysis
> tools add further confidence in the codebase by eliminating common classes of
> errors and enforcing a consistency which facilitates systematic and effective
> maintenance.
> 
> Additional tools are being developed to aid in the compliance route. A team at
> Hitachi, for example, is developing code minimization tooling to help minimize
> the lines of code which are included in the scope of the certification.
> 
> I believe understanding the ways in which our processes are being used to
> qualify Linux based safety critical systems is important for every maintainer to
> have. There may also be opportunity to incorporate some of this tooling into the
> mainstream development and reduce the need for secondary tooling. Even in this
> early stage, a stream of patches emerging from API compliance checkers has
> already found its way into the mainline kernel. The attendees are sure to have
> insight into their subsystem which will lead to improved analysis.
> 
> Potential Participants:
>   Darren Hart
>   Nicholas Mc Guire
>   Thomas Gleixner
>   Linus Walleij
>   Jason Cooper

I'm interested in this too.

Thanks,
Rafael

  reply	other threads:[~2016-07-29 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 20:25 Darren Hart
2016-07-29 20:48 ` Rafael J. Wysocki [this message]
2016-07-30  3:00 ` Steven Rostedt
2016-07-31 17:01   ` Shuah Khan

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=39739692.jqz6N0cLYc@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=der.herr@hofr.at \
    --cc=dvhart@infradead.org \
    --cc=jason@lakedaemon.net \
    --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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox