From: Sookyung Ahn <sookyung.ahn@boeing.com>
To: xen-devel@lists.xenproject.org
Cc: matthew.l.weber3@boeing.com, joshua.c.whitehead@boeing.com,
Anderson.Choi@boeing.com, brian.j.wood2@boeing.com,
haesun.kim@boeing.com, Sookyung Ahn <sookyung.ahn@boeing.com>
Subject: [RFC PATCH 0/2] Propose an minimal xen-tools
Date: Wed, 14 May 2025 07:12:48 +0000 [thread overview]
Message-ID: <cover.1747205627.git.sookyung.ahn@boeing.com> (raw)
I am writing to propose an enhancement to the `xen-tools` for users who require only a minimal subset of its functionality, particularly in safety-critical domains like aerospace.
I believe that the addition of a new build-time option, `ENABLE_MINIMAL_XEN_TOOLS`, will significantly benefit users by allowing them to build only the essential components needed for their specific applications.
This approach not only streamlines the toolset but also reduces the potential for unnecessary complexity in safety-critical environments.
This proposal is based on `dom0less` environment.
The proposed implementation includes:
- Introducing the `ENABLE_MINIMAL_XEN_TOOLS` configuration flag.
- Modifying the build process to selectively include only the necessary components based on the configuration.
This implementation can be effectively applied to the following use cases.
- Minimal APIs for `dom0less` operation. This involves taking existing Xen functions and shrinking them to minimal needed parts. For example, we can use static device tree instead of XenStore.
- By retaining `libxencall` and minimum part of `libxencrtl`, the Hypercall interface can be utilized, enabling support for the Xen ARINC653 Multiple Module Schedules service.
- Addition of ARINC653 Part1&2 APIs and services (hosted on the domain OS.)
I would appreciate any feedback or suggestions you may have regarding this enhancement.
Additionally, I would like to emphasize the importance of community input in refining this proposal to ensure it meets the needs of all users.
Sookyung Ahn (2):
changes for minimal-xen-tools
add document minimal_xen_tools.pandoc
config/Tools.mk.in | 1 +
docs/designs/minimal_xen_tools.pandoc | 147 ++++++++++++++++++++++++++
tools/Makefile | 19 ++++
tools/Rules.mk | 9 +-
tools/configure.ac | 47 +++-----
tools/flask/Makefile | 4 +
tools/hotplug/Linux/Makefile | 6 ++
tools/hotplug/Linux/systemd/Makefile | 6 ++
tools/libs/Makefile | 9 ++
tools/libs/ctrl/Makefile.common | 92 +++++++++-------
tools/libs/ctrl/xc_private.c | 6 ++
tools/libs/ctrl/xc_private.h | 7 +-
tools/libs/uselibs.mk | 76 +++++++------
13 files changed, 325 insertions(+), 104 deletions(-)
create mode 100644 docs/designs/minimal_xen_tools.pandoc
--
2.34.1
next reply other threads:[~2025-05-14 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 7:12 Sookyung Ahn [this message]
2025-05-14 7:12 ` [RFC PATCH 1/2] changes for minimal-xen-tools Sookyung Ahn
2025-05-14 7:12 ` [RFC PATCH 2/2] add document minimal_xen_tools.pandoc Sookyung Ahn
2025-05-14 7:28 ` Jan Beulich
2025-05-14 7:24 ` [RFC PATCH 0/2] Propose an minimal xen-tools Jan Beulich
2025-05-21 14:26 ` Anthony PERARD
2025-07-08 18:45 ` [EXTERNAL] " Weber (US), Matthew L
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=cover.1747205627.git.sookyung.ahn@boeing.com \
--to=sookyung.ahn@boeing.com \
--cc=Anderson.Choi@boeing.com \
--cc=brian.j.wood2@boeing.com \
--cc=haesun.kim@boeing.com \
--cc=joshua.c.whitehead@boeing.com \
--cc=matthew.l.weber3@boeing.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.