Nataliya Korovkina via Stratos-dev <stratos-dev(a)op-lists.linaro.org> writes:
> Hello,
>
> I'm going to look into the STR-11 task, specifically into Zephyr Dom0
> on Cortex-A. Will be glad to synchronize with other people who watch
> the task as well.
Hi Nataliya,
That's awesome :-)
Can I introduce you to Akashi-san (cc'ed) who has also been looking at
Zephyr on Xen and I believe already has some patches to make things work
better. I assume you already know Stefano who has a bunch of the work on
scoping out this use case in the STR-11 card.
I have a few questions:
- Are you also interested in the R-profile deployments (where the VMM
sits in it's own safety island dedicated to the VMM)?
- What platform are you considering for your implementation?
We also have a regular open fortnightly Stratos call if you want to sync up
with others in the community and discuss any technical issues.
Thanks,
--
Alex Bennée
Hello,
I'm going to look into the STR-11 task, specifically into Zephyr Dom0
on Cortex-A. Will be glad to synchronize with other people who watch
the task as well.
Thanks,
Nataliya
Interesting to attend this one I think
---------- Forwarded message ---------
From: UEFI Administration <admin(a)uefi.org>
Date: Wed, 18 Nov 2020 at 23:59
Subject: Last UEFI Forum Webinar of 2020: Virtual Firmware for Intel Trust
Domain Extensions
To: <contributor(a)uefi.org>
Cc: UEFI Administration <admin(a)uefi.org>
*UEFI 2020 Virtual Plugfest Webinar: **Virtual Firmware for Intel Trust
Domain Extensions* <https://www.brighttalk.com/webcast/18206/453600>
*Tuesday, December 15, 2020*
* Registration Now Open*
Hello UEFI Forum Members,
We would like to invite you to register for the upcoming *Virtual Firmware
for Intel Trust Domain Extensions webinar*
<https://www.brighttalk.com/webcast/18206/453600> apart of the UEFI 2020
Virtual Plugfest <https://uefi.org/node/4051>. This is your last chance to
attend a UEFI Forum hosted webinar in 2020.
The webinar, presented by Jiewen Yao of Intel, will introduce Intel Trust
Domain Extensions Virtual Firmware architecture and cover how it records
runtime measurements, manages private memory and more.
The webinar will include a live, interactive Q&A discussion on WebEx with
the presenter immediately following the presentation. Attendees will have
the chance to ask questions and participate in a lively discussion.
Register for the free, public webinar:
*Virtual Firmware for Intel Trust Domain Extensions*
<https://www.brighttalk.com/webcast/18206/453600>
*Tuesday, December 15, 2020 *
*Webinar Airing from 8:00 am – 9:00 am PT*
*Interactive Q&A from 9:00 am – 9:30 am PT*
Intel® Trust Domain Extensions (Intel® TDX) introduce architectural
elements to help deploy hardware-isolated, virtual machines (VMs) called
trust domains (TDs). Intel TDX is designed to isolate VMs from the
virtual-machine manager (VMM)/hypervisor and any other non-TD software on
the platform to protect TDs from a broad range of software.
This presentation introduces the architecture for TDX Virtual Firmware
(TDVF), and the firmware reference implementation available in open source.
The talk covers how TDVF runs from the TD reset vector, records runtime
measurements, manages private memory, interacts with the Intel TDX module
in Secure Arbitration Mode (SEAM), and loads the operating system (OS).
*Register for the webinar: *https://www.brighttalk.com/webcast/18206/453600
*Live WebEx Q&A information: *
-
https://nereus-587.my.webex.com/nereus-587.my/j.php?MTID=m4c27dc95e19f0c58f…
- Meeting number: 126 544 0541
- Password: q2TPMRqMw36 (72876776 from phones and video systems)
If you have any questions, please contact the UEFI Forum public relations
team at press(a)uefi.org.
Best Regards,
The UEFI Forum PR Team
--
François-Frédéric Ozog | *Director Linaro Edge & Fog Computing Group*
T: +33.67221.6485
francois.ozog(a)linaro.org | Skype: ffozog
Hi All
The December 2nd agenda has an interesting item relating to OP-TEE and
Virtualization; a slide deck has now been attached for this item.
https://collaborate.linaro.org/display/STR/Stratos+Home
Mike
--
Mike Holmes | Director, Foundation Technologies, Linaro
Mike.Holmes(a)linaro.org <mike.holmes(a)linaro.org>
"Work should be fun and collaborative, the rest follows"
Hi,
There are two parts to this series, broadly related because they are
all to do with Xen. The first half is a re-spin of the guest-loader
patches from a few weeks ago. The only changes are to move the
generic-loader documentation into the manual and then add some words
about the guest-loader.
The second half of the series is an attempt to fix and then clean up
the handling of Xen enabled builds. Recent changes to the build system
broke the ability to build qemu-system-i386 on arm64 hosts with Xen
support enabled. The actual fix for that:
meson.build: fix building of Xen support for aarch64
should probably be rolled into the current release as it fixes a
regression. The rest can wait until the tree re-opens. The patches
broadly try to:
- clean-up detection and reporting
- be more explicit about linking stubs for accel
- add an explicit CONFIG_XEN_HVM for x86
and finally allow you to build a qemu-system-aarch64 with Xen support.
This is my first major foray into tweaking meson builds and it seems
to occasionally come unstuck and requires a distclean and re-configure
to un-wedge itself. The following need review:
- meson.build: build a Xen aware qemu-aarch64-system
- xen: only build HVM support under CONFIG_XEN_HVM
- accel/stubs: drop unused cpu.h include
- stubs/xen-hw-stub: drop xenstore_store_pv_console_info stub
- include/hw/xen.h: drop superfluous struct
- meson.build: clean-up summary reporting of XEN and it's features
- meson.build: introduce CONFIG_XEN_HVM flag
- meson.build: fix building of Xen support for aarch64
- accel/meson: you only need accelerator stubs for softmmu builds
- docs: add some documentation for the guest-loader
- docs: move generic-loader documentation into the main manual
Alex Bennée (15):
hw/board: promote fdt from ARM VirtMachineState to MachineState
hw/riscv: migrate fdt field to generic MachineState
device_tree: add qemu_fdt_setprop_string_array helper
hw/core: implement a guest-loader to support static hypervisor guests
docs: move generic-loader documentation into the main manual
docs: add some documentation for the guest-loader
accel/meson: you only need accelerator stubs for softmmu builds
meson.build: fix building of Xen support for aarch64
meson.build: introduce CONFIG_XEN_HVM flag
meson.build: clean-up summary reporting of XEN and it's features
include/hw/xen.h: drop superfluous struct
stubs/xen-hw-stub: drop xenstore_store_pv_console_info stub
accel/stubs: drop unused cpu.h include
xen: only build HVM support under CONFIG_XEN_HVM
meson.build: build a Xen aware qemu-aarch64-system
docs/generic-loader.txt | 92 ----------
docs/system/generic-loader.rst | 117 ++++++++++++
docs/system/guest-loader.rst | 54 ++++++
docs/system/index.rst | 2 +
meson.build | 24 ++-
hw/core/guest-loader.h | 34 ++++
include/hw/arm/virt.h | 1 -
include/hw/boards.h | 1 +
include/hw/riscv/virt.h | 1 -
include/hw/xen/xen.h | 2 +-
include/sysemu/device_tree.h | 17 ++
include/sysemu/xen-mapcache.h | 2 +-
include/sysemu/xen.h | 9 +-
accel/stubs/hax-stub.c | 1 -
accel/stubs/xen-all-stub.c | 11 ++
accel/stubs/xen-stub.c | 2 -
hw/arm/virt.c | 322 +++++++++++++++++----------------
hw/core/guest-loader.c | 140 ++++++++++++++
hw/riscv/virt.c | 20 +-
softmmu/device_tree.c | 26 +++
stubs/xen-hw-stub.c | 4 -
accel/Kconfig | 3 +
accel/meson.build | 4 +-
accel/stubs/meson.build | 13 +-
hw/core/meson.build | 2 +
hw/i386/xen/meson.build | 2 +-
26 files changed, 627 insertions(+), 279 deletions(-)
delete mode 100644 docs/generic-loader.txt
create mode 100644 docs/system/generic-loader.rst
create mode 100644 docs/system/guest-loader.rst
create mode 100644 hw/core/guest-loader.h
create mode 100644 accel/stubs/xen-all-stub.c
create mode 100644 hw/core/guest-loader.c
--
2.20.1
Hi
I discovered the program and "Safety and Security with Virtual Open
Systems" use case is quite interesting:
https://www.arm.com/why-arm/technologies/safety?_ga=2.246792964.1846358630.…
Cheers
FF
--
François-Frédéric Ozog | *Director Linaro Edge & Fog Computing Group*
T: +33.67221.6485
francois.ozog(a)linaro.org | Skype: ffozog
This event has been changed.
Title: Project Stratos Sync
Discuss the latest Project Stratos devlopments.Mailing
listhttps://op-lists.linaro.org/mailman/listinfo/stratos-devAgenda - feel
free to suggest items on the mailing
listhttps://collaborate.linaro.org/display/STR/Meeting+notesPrevious
AgendaVirtualization infrastructure enhancements Agenda
When: Every 2 weeks from 4pm to 5:05pm on Thursday from Thu 6 Aug to Wed 25
Nov United Kingdom Time (changed)
Joining info: Join with Google Meet
https://meet.google.com/uak-yrcj-tyd
Join by phone
(GB) +44 20 3956 3214 (PIN: 706606273)
More phone numbers: https://tel.meet/uak-yrcj-tyd?pin=4387074781142&hs=0
Calendar: stratos-dev(a)op-lists.linaro.org
Who:
* Mike Holmes- organiser
* souvik.chakravarty(a)arm.com
* Joakim Bech
* bogdan.costinescu(a)nxp.com
* Anmar Oueja
* sreemeno(a)qti.qualcomm.com
* tsoni(a)quicinc.com
* Tom Gall
* pratikp(a)quicinc.com
* Sumit Semwal
* David Brazdil
* François Ozog
* ilias.apalodimas(a)linaro.org
* Bill Fletcher
* svaddagi(a)qti.qualcomm.com
* srinivas.kalaga(a)huawei.com
* David Rusling
* Don Harbin
* shashi.mallela(a)linaro.org
* atouzni(a)qti.qualcomm.com
* randy.linnell(a)linaro.org
* Sandeep Patil
* matt.spencer(a)arm.com
* ruchika.gupta(a)linaro.org
* victor.duan(a)linaro.org
* bogdan.vlad(a)nxp.com
* adelva(a)google.com
* peng.fan(a)nxp.com
* stratos-dev(a)op-lists.linaro.org
* Mathieu Poirier
* Alex Bennée
* ed.doxat(a)arm.com
* Mark Orvek
* sramana(a)qti.qualcomm.com
* satyakim(a)qti.qualcomm.com
Event details:
https://calendar.google.com/calendar/event?action=VIEW&eid=NXZzczhsdjNkbTVs…
Invitation from Google Calendar: https://calendar.google.com/calendar/
You are receiving this courtesy email at the account
stratos-dev(a)op-lists.linaro.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively, you can sign up for a Google Account at
https://calendar.google.com/calendar/ and control your notification
settings for your entire calendar.
Forwarding this invitation could allow any recipient to send a response to
the organiser and be added to the guest list, invite others regardless of
their own invitation status or to modify your RSVP. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
This event has been cancelled with this note:
"Moved 1 hour later and out to the 10th of December to avoid Thanksgiving
whilst not repeating on top of OpenMP and TF calls."
Title: Project Stratos Sync
Discuss the latest Project Stratos devlopments.Mailing
listhttps://op-lists.linaro.org/mailman/listinfo/stratos-devAgenda - feel
free to suggest items on the mailing
listhttps://collaborate.linaro.org/display/STR/Meeting+notesPrevious
AgendaVirtualization infrastructure enhancements Agenda
When: Every 2 weeks from 4pm to 5pm on Thursday United Kingdom Time
Joining info: Join with Google Meet
https://meet.google.com/uak-yrcj-tyd
Join by phone
(GB) +44 20 3956 3214 (PIN: 706606273)
More phone numbers: https://tel.meet/uak-yrcj-tyd?pin=4387074781142&hs=0
Calendar: stratos-dev(a)op-lists.linaro.org
Who:
* Mike Holmes- organiser
Invitation from Google Calendar: https://calendar.google.com/calendar/
You are receiving this courtesy email at the account
stratos-dev(a)op-lists.linaro.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively, you can sign up for a Google Account at
https://calendar.google.com/calendar/ and control your notification
settings for your entire calendar.
Forwarding this invitation could allow any recipient to send a response to
the organiser and be added to the guest list, invite others regardless of
their own invitation status or to modify your RSVP. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
Another consideration, next week is Thanksgiving in the US, I propose we
move the meeting until the week after.
MIke
On Tue, Nov 17, 2020 at 10:25 AM Mike Holmes via Stratos-dev <
stratos-dev(a)op-lists.linaro.org> wrote:
> Hi Stefano
>
> For the Linaro participants, it looks like one hour later is fine. if there
> are no objections I will move the meeting tomorrow.
>
> Mike
>
> On Mon, Nov 16, 2020 at 10:33 PM Stefano Stabellini <
> stefano.stabellini(a)xilinx.com> wrote:
>
> > Hi all,
> >
> > I would like to suggest having the Stratos meetings again at 8AM
> > California time / 4PM UK time to make it easier for people on the West
> > Coast to participate. (So far, we have been meeting mostly at 8AM,
> > except for a couple of occurrences.)
> >
> > Thanks for your help! :-)
> >
> > Cheers,
> >
> > Stefano
> >
>
>
> --
> Mike Holmes | Director, Foundation Technologies, Linaro
> Mike.Holmes(a)linaro.org <mike.holmes(a)linaro.org>
> "Work should be fun and collaborative, the rest follows"
> --
> Stratos-dev mailing list
> Stratos-dev(a)op-lists.linaro.org
> https://op-lists.linaro.org/mailman/listinfo/stratos-dev
>
--
Mike Holmes | Director, Foundation Technologies, Linaro
Mike.Holmes(a)linaro.org <mike.holmes(a)linaro.org>
"Work should be fun and collaborative, the rest follows"
Hi Alex, Arnd, Jean-Philippe, and all,
During the OpenAMP App-services call this week WindRiver gave a couple
of extremely interesting presentations, see attached slides.
Dan Milea discussed the usage of virtio between heterogeneous clusters,
i.e. virtio frontends on the Cortex-R cluster and virtio backends on
the Cortex-A cluster. They used a setup based on pre-shared memory to
make it work, which I believe is similar to the swiotlb approach we
discussed in Stratos. They noted that the last version of the virtio
spec on github had something in regards to virtio and pre-shared memory
regions that might help us cover this use-case from a spec perspective.
Dan, would you be able to share a pointer to it for clarity? So far, we
acted on the assumption that the virtio spec doesn't allow for this
architecture today; it would be fantastic if it turns out that it
already does.
The other very interesting presentation by Joshua Pincus was about
virtio-mmio and MSIs. They did excellent measurements on the
performance of virtio-mmio and they found out that the single source of
notifications (one interrupt) is the bottleneck. Adding MSIs vastly
improved performance. You can see the detailed breakdown on slide #8 of
"OpenAMP Virt I/O MMIO w/ MSI". This analysis really points in the
direction of adding MSIs to virtio-mmio.
Cheers,
Stefano
---------- Forwarded message ----------
Date: Wed, 28 Oct 2020 18:41:09 +0000
From: Nathalie Chan King Choy via App-services
<app-services(a)lists.openampproject.org>
Reply-To: Nathalie Chan King Choy <nathalie(a)xilinx.com>
To: "app-services(a)lists.openampproject.org"
<app-services(a)lists.openampproject.org>
Subject: [App-services] 2020-10-27 OpenAMP App-services call recording, notes,
slides, and action items
Hi all,
The notes from yesterday’s OpenAMP App-services call can be found at:
https://github.com/OpenAMP/open-amp/wiki/OpenAMP-Application-Services-Subgr…
The link to the Webex recording is in the notes. I am not sure how long before the recordings expire or I will hit my storage limit, so if
you need to catch up by watching the recording, please download it in the next couple weeks.
Please find attached the slides from Dan & Josh.
Action items:
* Dan & Josh to send slides (DONE)
* Stefano to start a thread w/ the folks who are working on shared memory & VirtIO
Best regards,
Nathalie C. Chan King Choy
Program Manager focused on Open Source and Community
--
App-services mailing list
App-services(a)lists.openampproject.org
https://lists.openampproject.org/mailman/listinfo/app-services