From: Stefano Stabellini <sstabellini@kernel.org>
To: fusa-sig@lists.xenproject.org
Cc: lars.kurth@citrix.com, sstabellini@kernel.org,
George.Dunlap@eu.citrix.com, lars.kurth.xen@gmail.com,
julien.grall@arm.com, xen-devel@lists.xenproject.org
Subject: [Xen-devel] list of Xen external interfaces for FuSa
Date: Mon, 17 Jun 2019 11:01:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1906171045560.2072@sstabellini-ThinkPad-T480s> (raw)
Hi all,
This is the list of external interfaces that we need to document for the
Xen FuSa work. I divided it into categories to make it easier to deal
with. The doc is also available in markdown format on github [1].
Cheers,
Stefano
[1] https://github.com/sstabellini/FuSa.git
---
# Intro
This document covers the external interfaces in a dom0less deployment
that we need to document for safety certifications.
Dom0 and Xen userspace tools, such as xl and libxl, are out of scope for
now, we are only discussing the hypervisor. vm_assist, xsm, argo are
also out of scope: the assumption is that they will disabled via
kconfig.
# From the user perspective
- Xen hypervisor command line options
- Dom0less device tree configuration
# Xen - Bootloader interfaces
- multiboot
- Xen boot protocol
# From a DomU perspective
- kernel image format
- boot protocol
- device tree
- memory map: location of memory and other resources
- exposed devices
- GIC interrupt controller
- Generic Timer
- virtual UART (PL011)
- PSCI
- hypercall protocol (i.e. registers, etc.)
- memory sharing (i.e. memory/cache attributes)
# Hypercalls exposed to all DomUs
These hypercalls are unused by dom0less domUs, however, they are
still exposed to all domUs.
- memory_op
- sched_op
- xen_version
- hvm_op
- multicall
- platform_op
- vcpu_op
- physdev_op (NOP on Arm)
# PV drivers interfaces
Dom0less domUs cannot use PV drivers today. However, these interfaces
are still exposed to them, and one day they might be able to use them
correctly:
- hypercalls
- console_io
- grant_table_op
- event_channel_op
- xenstore
- xenstore initialization
- xenstore protocol
- message format
- notifications
- xenstore as a bus
- PV protocols
- PV console
- PV network
- PV block
# Privileged hypercalls (dom0 and toolstack)
- domctl
- sysctl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2019-06-17 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.21.1906171045560.2072@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=fusa-sig@lists.xenproject.org \
--cc=julien.grall@arm.com \
--cc=lars.kurth.xen@gmail.com \
--cc=lars.kurth@citrix.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 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).