From: Rich Persaud <persaur@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Artem_Mygaiev@epam.com, Robin.Randhawa@ARM.com,
Chris Patterson <pattersonc@ainfosec.com>,
yaroslav.bublykarvind@globallogic.com, Alex_Agizim@epam.com,
Stewart.Hildebrand@dornerworks.com,
Daniel Bernal <Daniel.Bernal@arm.com>,
sstabellini@kernel.org,
Jonathan Kline <jonathan.kline@starlab.io>,
arvind.murthy@globallogic.com, denys.balatsko@globallogic.com
Subject: Xen for Automotive - white paper on virtualization - Call at 1600 UTC, Mon 5th Feb
Date: Thu, 1 Feb 2018 22:36:59 -0500 [thread overview]
Message-ID: <EFB1BA1D-EB72-4896-ABA3-5ABA7EE9DBB5@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 823 bytes --]
Over the next few weeks, the Automotive Grade Linux (AGL) community will draft a white paper [1] on virtualization. I'm assisting Lars with coordination of Xen contributions. Here is a summary of discussions preceding this message:
https://docs.google.com/document/d/1-_Uyi46L2jqrNKyOxo4GLI4IWD3jg2GTDJgVvhsvpd4
If you can help communicate the benefits of Xen as a component of safety-certified automotive solutions, please reply to this thread and/or attend the Xen community conference call next Monday, 5th February at 0800 PST / 1100 EST / 1600 UTC / 1700 CET.
Join the call: https://www.uberconference.com/stefano-stabellini
Optional dial in number: +1-669-999-0613
No PIN needed
Thanks,
Rich
[1] https://wiki.automotivelinux.org/eg-virt-meetings?&#january_26th_2018_2pm_cet_meeting
[-- Attachment #1.2: Type: text/html, Size: 3099 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-02-02 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 3:36 Rich Persaud [this message]
2018-07-12 12:39 ` Xen for Automotive - white paper on virtualization Rich Persaud
2018-07-12 14:55 ` Michele Paolino
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=EFB1BA1D-EB72-4896-ABA3-5ABA7EE9DBB5@gmail.com \
--to=persaur@gmail.com \
--cc=Alex_Agizim@epam.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Daniel.Bernal@arm.com \
--cc=Robin.Randhawa@ARM.com \
--cc=Stewart.Hildebrand@dornerworks.com \
--cc=arvind.murthy@globallogic.com \
--cc=denys.balatsko@globallogic.com \
--cc=jonathan.kline@starlab.io \
--cc=pattersonc@ainfosec.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yaroslav.bublykarvind@globallogic.com \
/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;
as well as URLs for NNTP newsgroup(s).