On 06.04.18 17:13, Lars Kurth wrote:
Hi all,

adding a few more people who are/may be interested in safety certification, 
including committers (because item 1 would have an impact). Specifically: Rich 
Persaud, Paul Luperto, Jonathan Daugherty and Denys Balatsko.

There are a few loose ends and updates from other/similar related threads that 
we should pull into this thread:

a) AGL Whitepaper
This is out as far as I can tell
See 
https://docs.google.com/document/d/1HpYzClh0nDEocsUHb17X0DxiehsAbCgyWE-P2Wk_RNU/edit#
Thank you to Rich for driving this and to all the contributors from the Xen 
Community

Related to this is the following item from the original minutes
AGL will select 2 hypervisors out of the list. Artem has already an
out-of-the-box solution for AGL. Artem will chase up and make sure that
Xen will be one of the two.

b) Genivi AMM Hypervisor Workshop, Apr 19
Artem and me will be speaking on various Xen related projects. I will send a 
draft PDF to this list later this week.
Slots are short: 10 minutes + questions each slot
See https://at.projects.genivi.org/wiki/display/DIRO/Hypervisor+Workshop+Team

c) Xen Specific Automotive Whitepaper
This was discussed during a) and I think it would be relatively easy to pull 
something together. It would be good if someone else, but me could lead this. 
We have a lot of information already, but more ground-work on safety 
certification may help. Would there be a volunteer driving this? I could be 
used as a vehicle to move some of the items discussed in the minutes along.


As there's a lot of overlap with what has been done for AGL & GENIVI I'll be happy to drive this.

d) I also created 
https://wiki.xenproject.org/wiki/Category:Safety_Certification to start pulling 
material relevant to safety and context for it into one place.
It's a little crude at this point in time and I expect this document to evolve 
and split into smaller parts.
It would be good, if someone on this list could go over 
https://wiki.xenproject.org/wiki/Category:Safety_Certification#Automotive_Requirements
 and map the requirements to functionality we already have. This could then 
feed into c.

Any takers?


I'll be happy to take this as well.

Artem suggested to write a whitepaper about Xen real-time capabilities.
Stefano volunteered to help.
I believe we have some gaps with regards to real-time requirements and that 
paper is aiming to highlight these.
@Artem: maybe this would be a suitable topic for the developer summit (amongst 
others)
As a reminder: the CfP for the summit closes next Friday
>

Yes, we plan to submit a talk re: RT based on the wp being prepared

I contacted Lars (CC'ed) who volunteered to help.
I am volunteering to act as a program/project manager for this activity. In 
particular to bootstrap.

I think the only practicable way to make progress in this area, is to set up 
some mechanism which allow us to make progress towards the goal of making it 
easier and cheaper to build safety certified variants of Xen. As a side-effect 
of this process we should get data, to scope out the scale of the problem 
further, that should enable getting more vendors interested.
The main topic of the meeting was certifications for Xen on ARM. The gap
analysis document, mentioned in the previous call, is copyrighted. It
might not be possible to relicense it. Regardless of the document, we
started discussing the major work items and next steps.

@Stefano: Thanks for driving this discussion
I re-ordered some of the items, to make it more palatable

2) Create a subset of functions that need to go through certifications
Next step: create a small Kconfig. We could use the Renesas Rcar as
reference. We need a discussion about the features we need, for example
real-time schedulers, do we need them or not?

@Stefano agreed to drive this.
The minimal configuration does impact 1 and 2, which is why I moved this first.

We should probably agree a basic process: aka
* Measure baseline size in KSLOC
* Remove some feature
* Measure reduction in KSLOC
And record the data somewhere
1) Requirements to the code, a subset of MISRA for ASIL B
Next step: get more information about requirements and publish it to
xen-devel.

I see a few problems here:

* The MISCRA 2012 spec has to be bought and it is rather big (100's of pages):
so, I don't think it is practical to work from the spec

* Some coding style patterns will likely be perceived as odd and unreasonable
by community members: as some common code would be affected we cannot
treat this in isolation say on ARM only. Although it is recognized that some of
the coding style patterns may not make sense, compliance to MISRA is
necessary and cannot normally be discussed away.

* PRQA has set up an environment and initial MISRA compliance report for a Xen 
on ARM build
** The question is what (if anything) can be shared publicly
** The other open question is whether we can come to some sort of longer term 
agreement between the Xen Project and PRQA to use their tools
** As an aside, what PRQA have done would need to reflect what we do in step 2 
is. We also want to minimize the work for PRQA: in other words, it has to be 
very simple to enable the minimal config coming out of task 2 such that PRQA can
** As far as I recall 90% of all MISRA violations come down to around 70 
issues. A large number are in tools
** Also, I believe that MISRA compliance tools will likely lead to a large 
amount of false positives, due to the distributed nature of Xen: process 
boundaries, kernel/user space boundaries, etc. would all lead to false 
positives, which somehow have to be managed.

ACTION => Lars to follow up with Paul Luperto from PRQA

* An approach that may be manageable would be to look at the most common MISRA 
violations and work backwards from there.
** This would make the problem more manageable and mean people wouldn't have to 
read a long spec
** Discussing a small set of issues, would give us a sense of whether/what type 
of disagreements there are and how we resolve them.
** We should focus prioritize based on:
a) Address/discuss the most frequently occurring issues first
b) Address/discuss issues in common code first

At the very least (and for now in absence of the capability to check 
compliance), I would need someone who has access to MISRA compliance tools, to 
drive such an effort.

3) Understand how to address dom0. FreeRTOS Dom0 sounds like a good
solution.
Next step: reach out to Dornerworks and/or others that worked with
FreeRTOS on Xen before. Figure out whether FreeRTOS is actually a
suitable solution and what needs to be done to run FreeRTOS as Dom0.

Some things to check at this stage:
a) I believe there is a safety certified version of FreeRTOS - I could not find 
much, except for 
https://www.freertos.org/FreeRTOS-Plus/Safety_Critical_Certified/SafeRTOS-Safety-Critical-Certification.shtml
 - which describes SafeRTOS a commercial safety certified FreeRTOS and (mostly) 
API compliant version of FreeRTOS. Or am I missing something here?
b) There is a DomU capable version from Galois (Jonathan Docherty CC'ed) - I 
don't know whether others also have such versions
c) There is a POXIX wrapper, which may be needed, but it is unclear what this 
would do to the FreeRTOS footprint
d) In other words, what we would have to do is to investigate whether it is 
possible to build to a Dom0 capable FreeRTOS

I see several ways of approaching this:
a) A vendor (or groups of vendors) on this list steps up
b) We go initially for a lower bar: aka we try and scope out and cost the 
creation of a Dom0 capable FreeRTOS and then look at how the work can get funded

A very good starting point would be to get a list of parties that are 
interested in having and using a FreeRTOS based Dom0 (regardless of how we get 
there). A show of hands would be good.
Some insights from anyone on the FreeRTOS/SafeRTOS relationship and politics 
would be good also. Unless there is a route from FreeRTOS upstream to the 
certified version, someone in our eco-system would have to safety certify 
FreeRTOS (which may not be such a big deal given the fairly small size of 
FreeRTOS).


We plan to analyze efforts to port FreeRTOS as dom0 OS

4) Create artifacts, such as docs, fault analysis, prove fault tolerance,
safety management docs, development processes.
Next step: we need to bring in a company, a certification body, to guide
us through the process.

We have companies such as Dornerworks on this list which are experienced with 
safety certification on Xen for some safety standards: it is not clear to me 
how much of this is transferable to automotive.

Here my understanding is that we need a certification partner like TÜV, MIRA or 
a company like Dornerworks who already have experience with Xen. By working 
with a partner experienced in certification, the overall cost of certification 
would be significantly reduced. The elephant in the room is funding and a 
business model (aka all the items listed in 
https://docs.google.com/document/d/1HpYzClh0nDEocsUHb17X0DxiehsAbCgyWE-P2Wk_RNU/edit
 section 4.1). The reality is that organisations such as TÜV, MIRA, 
Dornerworks, ... will need to be paid by someone. Which, I think we need to 
park for now.

What I think are sensible goals for now are
a) Establish a list of potential partners and start establishing contacts - 
such conversations would need to be led by a vendor, otherwise it will go 
nowhere. What would be good though is to have a shared (but possibly private) 
repository of how these conversations have gone.
b) Otherwise focus on tasks 1-3 which deal with some issues listed in 
https://www.slideshare.net/xen_com_mgr/art-certification, which is still very 
valid
c) Engage/work with with other groups (AGL, Genivi, Linaro) who are also 
looking at this problem

It may be worth in the mid-term to consider some sort of pilot around a small 
portion of the Xen codebase: the aim would be to gather data that helps 
establish what can be done in a collaborative FOSS environment.

Feedback/views are very welcome

Regards
Lars


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to