From: Michele Paolino <m.paolino@virtualopensystems.com>
To: Rich Persaud <persaur@gmail.com>
Cc: Artem Mygaiev <Artem_Mygaiev@epam.com>,
Daniel Bernal <Daniel.Bernal@arm.com>,
Alex Agizim <Alex_Agizim@epam.com>,
Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
sstabellini@kernel.org,
Jonathan Kline <jonathan.kline@starlab.io>,
xen-devel@lists.xenproject.org,
Denys Balatsko <denys.balatsko@globallogic.com>
Subject: Re: Xen for Automotive - white paper on virtualization
Date: Thu, 12 Jul 2018 16:55:35 +0200 [thread overview]
Message-ID: <CAFMr_pQVwvYYeHwfKD7Qn1XN+aFHQh-CWjJLDqaH9+VjRfYD5Q@mail.gmail.com> (raw)
In-Reply-To: <9F2A9589-6324-4D7A-85FD-CB93D8708FEB@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
Thank you Rich to share this with the XEN community,
Any comment is welcome.
Regards,
On Thu, Jul 12, 2018 at 2:39 PM, Rich Persaud <persaur@gmail.com> wrote:
> Thanks to everyone who contributed to the AGL virtualization white paper
> and to Michele Paolino for stewarding it from concept to final publication.
> I’ve added it to the Xen wiki:
>
> https://wiki.xenproject.org/wiki/Automotive_Whitepapers
>
> Rich
>
--
*Michele Paolino, Virtualization Architect*
*Virtual Open Systems SASMixed-Critical Virtualization Solutions*
*Automotive | IoT-Edge | Embedded Systems*
*Web: www.virtualopensystems.com <http://www.virtualopensystems.com>*
[-- Attachment #1.2: Type: text/html, Size: 2204 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
prev parent reply other threads:[~2018-07-12 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 3:36 Xen for Automotive - white paper on virtualization - Call at 1600 UTC, Mon 5th Feb Rich Persaud
2018-07-12 12:39 ` Xen for Automotive - white paper on virtualization Rich Persaud
2018-07-12 14:55 ` Michele Paolino [this message]
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=CAFMr_pQVwvYYeHwfKD7Qn1XN+aFHQh-CWjJLDqaH9+VjRfYD5Q@mail.gmail.com \
--to=m.paolino@virtualopensystems.com \
--cc=Alex_Agizim@epam.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Daniel.Bernal@arm.com \
--cc=Stewart.Hildebrand@dornerworks.com \
--cc=denys.balatsko@globallogic.com \
--cc=jonathan.kline@starlab.io \
--cc=persaur@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).