From: Anshul Makkar <anshul.makkar@citrix.com>
To: xen-devel@lists.xen.org
Cc: dgdegra@tycho.nsa.gov, Anshul Makkar <anshul.makkar@citrix.com>
Subject: [PATCH] XSM-docs: Flask operates on domain types and not on individual domain. Updated the documentation to reflect this.
Date: Tue, 19 Jul 2016 10:05:34 +0100 [thread overview]
Message-ID: <1468919134-7603-1-git-send-email-anshul.makkar@citrix.com> (raw)
Signed-off-by: Anshul Makkar <anshul.makkar@citrix.com>
---
* Resending the patch due to incomplete subject in the previous patch.
docs/misc/xsm-flask.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
---
diff --git a/docs/misc/xsm-flask.txt b/docs/misc/xsm-flask.txt
index 62f15dd..bf8bb6e 100644
--- a/docs/misc/xsm-flask.txt
+++ b/docs/misc/xsm-flask.txt
@@ -9,8 +9,8 @@ controls over Xen domains, allowing the policy writer to define what
interactions between domains, devices, and the hypervisor are permitted.
Some examples of what FLASK can do:
- - Prevent two domains from communicating via event channels or grants
- - Control which domains can use device passthrough (and which devices)
+ - Prevent two domains types from communicating via event channels or grants
+ - Control which type of domains can use device passthrough (and which devices)
- Restrict or audit operations performed by privileged domains
- Prevent a privileged domain from arbitrarily mapping pages from other domains
@@ -160,10 +160,10 @@ the policy can be reloaded using "xl loadpolicy".
The example policy included with Xen demonstrates most of the features of FLASK
that can be used without dom0 disaggregation. The main types for domUs are:
- - domU_t is a domain that can communicate with any other domU_t
+ - domU_t is a domain type that can communicate with any other domU_t types.
- isolated_domU_t can only communicate with dom0
- prot_domU_t is a domain type whose creation can be disabled with a boolean
- - nomigrate_t is a domain that must be created via the nomigrate_t_building
+ - nomigrate_t is a domain type that must be created via the nomigrate_t_building
type, and whose memory cannot be read by dom0 once created
HVM domains with stubdomain device models also need a type for the stub domain.
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-07-19 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 9:05 Anshul Makkar [this message]
2016-07-19 13:30 ` [PATCH] XSM-docs: Flask operates on domain types and not on individual domain. Updated the documentation to reflect this Doug Goldstein
2016-07-19 15:21 ` anshul makkar
2016-07-19 15:29 ` Daniel De Graaf
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=1468919134-7603-1-git-send-email-anshul.makkar@citrix.com \
--to=anshul.makkar@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--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 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).