From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>, xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v6 2/2] xsm: add a default policy to .init.data
Date: Thu, 14 Jul 2016 15:28:20 +0100 [thread overview]
Message-ID: <eb4428f2-0be0-901b-6296-0816e1abcf3f@citrix.com> (raw)
In-Reply-To: <1468505927-5340-2-git-send-email-dgdegra@tycho.nsa.gov>
On 14/07/16 15:18, Daniel De Graaf wrote:
> This adds a Kconfig option and support for including the XSM policy from
> tools/flask/policy in the hypervisor so that the bootloader does not
> need to provide a policy to get sane behavior from an XSM-enabled
> hypervisor. The policy provided by the bootloader, if present, will
> override the built-in policy.
>
> The XSM policy is not moved out of tools because that remains the
> primary location for installing and configuring the policy.
>
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-14 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 14:18 [PATCH v6 1/2] xsm: rework policy_buffer globals Daniel De Graaf
2016-07-14 14:18 ` [PATCH v6 2/2] xsm: add a default policy to .init.data Daniel De Graaf
2016-07-14 14:28 ` Andrew Cooper [this message]
2016-07-14 14:26 ` [PATCH v6 1/2] xsm: rework policy_buffer globals Andrew Cooper
2016-07-14 15:07 ` Andrew Cooper
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=eb4428f2-0be0-901b-6296-0816e1abcf3f@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.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).