All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	davorin.mista@aggios.com, robin.randhawa@arm.com,
	Artem Mygaiev <Artem_Mygaiev@epam.com>,
	Matt.Spencer@arm.com, anastassios.nanos@onapp.com,
	julien.grall@arm.com,
	Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
	xen-devel@lists.xenproject.org, vfachin@de.adit-jv.com,
	Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
	mirela.simonovic@aggios.com,
	Jarvis Roach <Jarvis.Roach@dornerworks.com>
Subject: Minutes of: Xen ARM Community Call Wednesday 25th July 9AM Pacific / 4PM UTC
Date: Wed, 25 Jul 2018 13:33:08 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1807251323050.20701@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <alpine.DEB.2.10.1807131249330.4709@sstabellini-ThinkPad-X260>

Hi Everyone,

These are the notes I took during the meeting. Thanks for attending!

Cheers,

Stefano

= Certifications =
Lars. Discussion at Xen Summit didn't go far because we didn't have any
concrete examples. Lars had a meeting with PRQA. The acquisition by
Perforce is completed. Lars sent all info by email last week to them,
they want to continue the engagement.

= Code reduction =
Completed, except for security support definition of the new kconfig
options.

= FreeRTOS / Zephyr Dom0 =
Don't know the state given that Artem is not available.  Zephyr has a
two tiers membership system: the top tier is for the certification
efforts. The artifact produced by the certification efforts are only
available to the tier-1 members. Need to follow up.

= Dom0less =
Stefano explains the latest. Device assignment is supported.
ACTION: Gather more details on use-cases.

= vTPM =
We'll have a call on this topic to discuss next steps.

= Power Management =
Stefano is reviewing power management patches to do system suspend. They
are in a good state. Device power management is not supported.
EEMI vs SCMI support for cpufreq/device PM. Not clear the impact on Xen
to support multiple firmware interfaces.

= Virtio =
Julien: we are looking at graphics virtualization in ARM. Virtio has a
PV graphic solution already. The main problem with not using virtio is
that we have to duplicate the transport layer every time. We spend time
to get drivers running instead of improving the drivers. Can we get
virtio running on Xen?

Concern #1: virtio removes the separation between frontend and backend.
There is a work in progress idea to add the concept of an IOMMU to
virtio, so that the backend needs only to be allowed to map the pages
with IOMMU mappings. It wouldn't need to be able to map any page in the
system anymore. It might make driver domains possible. Stefano is
concerned about splitting the community.

Lars says that Genivi is talking about virtio. Christopher: if we are
going to use virtio, why not use KVM too?
ACTION: Christopher to join Genivi meetings to explain the issues with
virtio.
Stefano: this is good because we want people to be informed and either
fix virtio or not use it at all.
Julien: Instead, they might simply not care about isolation.
Lars: No, they do care. During one of the last meetings they
highlighted isolation as a concern. The other concern is that the
emulators are QEMU based.

References:
cpufreq:
https://www.slideshare.net/xen_com_mgr/xpdds18-cpufreq-in-xen-on-arm-oleksandr-tyshchenko-epam-systems
https://www.youtube.com/watch?v=ZimfN52wkcM&index=15&list=PLYyw7IQjL-zFlQYbY9BgsLhxqp1Ui67W7
Genivi meeting and info:
https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=16026657
https://at.projects.genivi.org/wiki/display/DIRO/Hypervisor+Project
Key Person: Gunnar Anderson

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

      parent reply	other threads:[~2018-07-25 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 20:12 Xen ARM Community Call Wednesday 25th July 9AM Pacific / 4PM UTC Stefano Stabellini
2018-07-24 18:01 ` Stefano Stabellini
2018-07-25 20:33 ` Stefano Stabellini [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=alpine.DEB.2.10.1807251323050.20701@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=Artem_Mygaiev@epam.com \
    --cc=Jarvis.Roach@dornerworks.com \
    --cc=Matt.Spencer@arm.com \
    --cc=Stewart.Hildebrand@dornerworks.com \
    --cc=anastassios.nanos@onapp.com \
    --cc=davorin.mista@aggios.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@citrix.com \
    --cc=mirela.simonovic@aggios.com \
    --cc=robin.randhawa@arm.com \
    --cc=vfachin@de.adit-jv.com \
    --cc=volodymyr_babchuk@epam.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.