All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Daniel P. Smith" <dpsmith@apertussolutions.com>
Cc: xen-devel@lists.xenproject.org,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Wei Liu <wl@xen.org>,
	scott.davis@starlab.io, jandryuk@gmail.com,
	christopher.clark@starlab.io,
	Luca Fancellu <luca.fancellu@arm.com>,
	Julien Grall <jgrall@amazon.com>,
	Rahul Singh <rahul.singh@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>,
	Bertrand Marquis <bertrand.marquis@arm.com>,
	Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Dario Faggioli <dfaggioli@suse.com>,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH v9 1/3] xsm: create idle domain privileged and demote after setup
Date: Thu, 30 Jun 2022 11:24:25 +0200	[thread overview]
Message-ID: <Yr1ryXy/mMi6tJzY@Air-de-Roger> (raw)
In-Reply-To: <20220630022110.31555-2-dpsmith@apertussolutions.com>

On Wed, Jun 29, 2022 at 10:21:08PM -0400, Daniel P. Smith wrote:
> There are new capabilities, dom0less and hyperlaunch, that introduce internal
> hypervisor logic, which needs to make resource allocation calls that are
> protected by XSM access checks. The need for these resource allocations are
> necessary for dom0less and hyperlaunch when they are constructing the initial
> domain(s).  This creates an issue as a subset of the hypervisor code is
> executed under a system domain, the idle domain, that is represented by a
> per-CPU non-privileged struct domain. To enable these new capabilities to
> function correctly but in a controlled manner, this commit changes the idle
> system domain to be created as a privileged domain under the default policy and
> demoted before transitioning to running. A new XSM hook,
> xsm_set_system_active(), is introduced to allow each XSM policy type to demote
> the idle domain appropriately for that policy type. In the case of SILO, it
> inherits the default policy's hook for xsm_set_system_active().
> 
> For flask, a stub is added to ensure that flask policy system will function
> correctly with this patch until flask is extended with support for starting the
> idle domain privileged and properly demoting it on the call to
> xsm_set_system_active().
> 
> Signed-off-by: Daniel P. Smith <dpsmith@apertussolutions.com>
> Reviewed-by: Jason Andryuk <jandryuk@gmail.com>
> Reviewed-by: Luca Fancellu <luca.fancellu@arm.com>
> Acked-by: Julien Grall <jgrall@amazon.com> # arm
> Reviewed-by: Rahul Singh <rahul.singh@arm.com>
> Tested-by: Rahul Singh <rahul.singh@arm.com>

LGTM:

Acked-by: Roger Pau Monné <roger.pau@citrix.com>

Thanks, Roger.


  reply	other threads:[~2022-06-30  9:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  2:21 [PATCH v9 0/3] Adds starting the idle domain privileged Daniel P. Smith
2022-06-30  2:21 ` [PATCH v9 1/3] xsm: create idle domain privileged and demote after setup Daniel P. Smith
2022-06-30  9:24   ` Roger Pau Monné [this message]
2022-06-30 14:10     ` Daniel P. Smith
2022-06-30  2:21 ` [PATCH v9 2/3] flask: implement xsm_set_system_active Daniel P. Smith
2022-06-30  2:21 ` [PATCH v9 3/3] xsm: refactor flask sid alloc and domain check Daniel P. Smith
2022-06-30  6:14   ` Jan Beulich
2022-06-30 14:09     ` Daniel P. Smith
2022-06-30  8:40   ` Henry Wang
2022-06-30 14:11     ` Daniel P. Smith
2022-07-05 13:03   ` Jason Andryuk
2022-07-05 17:35     ` Daniel P. Smith
2022-07-06 19:13       ` [RFC PATCH] flask: Remove magic SID setting Jason Andryuk
2022-07-07 10:12         ` Daniel P. Smith
2022-07-07 12:45           ` Jason Andryuk
2022-07-10  2:58             ` Daniel P. Smith
2022-06-30 22:35 ` [PATCH v9 0/3] Adds starting the idle domain privileged Stefano Stabellini
2022-07-01  0:11   ` Daniel P. Smith
2022-07-01 10:24   ` Jan Beulich
2022-07-01 17:56     ` Stefano Stabellini

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=Yr1ryXy/mMi6tJzY@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bertrand.marquis@arm.com \
    --cc=christopher.clark@starlab.io \
    --cc=dfaggioli@suse.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=dpsmith@apertussolutions.com \
    --cc=george.dunlap@citrix.com \
    --cc=jandryuk@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=jgrall@amazon.com \
    --cc=julien@xen.org \
    --cc=luca.fancellu@arm.com \
    --cc=rahul.singh@arm.com \
    --cc=scott.davis@starlab.io \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --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.