All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Smith" <dpsmith.dev@gmail.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: "James McKenzie" <james.mckenzie@bromium.com>,
	"robin.randhawa@arm.com" <robin.randhawa@arm.com>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	"Daniel P. Smith" <dpsmith@apertussolutions.com>,
	"Doug Goldstein" <cardoe@cardoe.com>,
	"Christopher Clark" <christopher.w.clark@gmail.com>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	"Lars Kurth" <lars.kurth.xen@gmail.com>,
	"Paul Durrant" <Paul.Durrant@citrix.com>,
	"committers@xenproject.org" <committers@xenproject.org>,
	"Jun Nakajima" <jun.nakajima@intel.com>,
	"Stewart Hildebrand" <Stewart.Hildebrand@dornerworks.com>
Subject: Enhancing Xen's Kconfig infrastructure to support tailored solutions
Date: Tue, 12 Feb 2019 21:34:25 -0500	[thread overview]
Message-ID: <a49643ec-6bbe-04be-1ae2-b1d731da92cf@gmail.com> (raw)

Greetings,

On the 11/14/18 Xen x86 community call a discussion was initiated about
using Kconfig to build minimized versions of Xen for security, safety
and other certification requirements. After some offline discussions
with Xen contributors I realized that a variety of efforts each with
their own respective goals are underway,

 - nested virtualization
 - mixed criticality architectures
 - reducing trusted componentary
 - combining hardware protection of virtualization with performance and
ease-of-use of containers

These efforts use hypervisors in different roles, all which Xen is
capable of meeting. Today Xen's utility comes at the expense of carrying
features necessary for one role to be present in another role where it
is not required, e.g. PV interfaces that may not be essential in an ARM
mixed criticality deployment.

The initial focus will be to explore and document the range of possible
use cases that are of interest to the Xen community. This will be the
input to a design document that is crafted in conjunction with the Xen
maintainers, to identify possible approaches to extend the existing
Kconfig infrastructure to produce tailored instances of Xen.

If you are interested in participating in this effort, please reply to
this thread to outline possible use cases, design constraints and other
considerations for improving Xen's Kconfig infrastructure to support
tailoring for specific use cases.

V/r,
Daniel P. Smith
Apertus Solutions, LLC

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

             reply	other threads:[~2019-02-13  2:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13  2:34 Daniel P. Smith [this message]
2019-02-13 11:13 ` Enhancing Xen's Kconfig infrastructure to support tailored solutions Jan Beulich
2019-02-13 18:25 ` Wei Liu
2019-02-13 19:11   ` Stefano Stabellini
2019-02-14  9:53     ` Jan Beulich
2019-02-14 18:32       ` Stefano Stabellini
2019-02-14 18:57         ` Andrew Cooper
2019-02-15  8:43           ` Jan Beulich
2019-02-14 21:03         ` Lars Kurth
2019-02-15 11:08           ` Wei Liu
2019-02-15 19:08             ` Stefano Stabellini
2019-02-18 11:12               ` Wei Liu
2019-02-18 11:17                 ` Lars Kurth
2019-02-18 11:23                   ` Wei Liu
2019-02-18 11:30                     ` George Dunlap
2019-02-18 11:53                       ` Lars Kurth
2019-02-18 11:57                         ` Wei Liu
2019-02-18 12:00                           ` Lars Kurth
2019-02-18 12:01                           ` Andrew Cooper
2019-02-18 12:11                             ` Lars Kurth
2019-02-18 12:11                             ` George Dunlap
2019-02-18 12:16                               ` George Dunlap
2019-02-18 12:54                                 ` Lars Kurth
2019-02-19 19:13                                   ` Stefano Stabellini
2019-02-19 21:05                                     ` P S
2019-02-15  8:52         ` Jan Beulich
2019-02-15 17:27           ` Stefano Stabellini
2019-02-15 10:58         ` Wei Liu
2019-02-14 18:52       ` Andrew Cooper
2019-02-15  9:35     ` George Dunlap
2019-02-15 11:10       ` Lars Kurth
2019-02-15 17:36       ` Stefano Stabellini
2019-02-15 17:55         ` George Dunlap
2019-02-15 18:27           ` Stefano Stabellini
2019-02-24 14:52       ` Daniel P. Smith

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=a49643ec-6bbe-04be-1ae2-b1d731da92cf@gmail.com \
    --to=dpsmith.dev@gmail.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=Stewart.Hildebrand@dornerworks.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=cardoe@cardoe.com \
    --cc=christopher.w.clark@gmail.com \
    --cc=committers@xenproject.org \
    --cc=dpsmith@apertussolutions.com \
    --cc=james.mckenzie@bromium.com \
    --cc=jun.nakajima@intel.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=robin.randhawa@arm.com \
    --cc=xen-devel@lists.xen.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.