From: fu.wei@linaro.org
To: xen-devel@lists.xensource.com, julien.grall@arm.com,
sstabellini@kernel.org, dgdegra@tycho.nsa.gov,
konrad.wilk@oracle.com, ian.jackson@eu.citrix.com,
jbeulich@suse.com, keir@xen.org, tim@xen.org,
xen-devel@lists.xen.org
Cc: jcm@redhat.com, Fu Wei <fu.wei@linaro.org>,
leif.lindholm@linaro.org, linaro-uefi@lists.linaro.org
Subject: [PATCH v2] docs/arm64: update the documention for loading XSM support
Date: Thu, 21 Apr 2016 19:07:09 +0800 [thread overview]
Message-ID: <1461236829-11491-1-git-send-email-fu.wei@linaro.org> (raw)
From: Fu Wei <fu.wei@linaro.org>
This patch updates the documentation for allowing detection of an XSM
module that lacks a specific compatible string.
This mechanism has been added by the commit
ca32012341f3de7d3975407fb963e6028f0d0c8b.
Signed-off-by: Fu Wei <fu.wei@linaro.org>
---
v2: Improve the doc, according to the suggestion from Julien Grall.
v1: http://lists.xen.org/archives/html/xen-devel/2016-04/msg02070.html
The first upstream version submitted in xen-devel mailing list.
docs/misc/arm/device-tree/booting.txt | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/docs/misc/arm/device-tree/booting.txt b/docs/misc/arm/device-tree/booting.txt
index ad98bf3..254ba77 100644
--- a/docs/misc/arm/device-tree/booting.txt
+++ b/docs/misc/arm/device-tree/booting.txt
@@ -24,10 +24,24 @@ Each node contains the following properties:
string (which must always be present).
Xen will assume that the first module which lacks a more
- specific compatible string is a "multiboot,kernel" and that
- the second such is a "multiboot,ramdisk". Any subsequent
- modules which lack a specific compatiblity string will not
- receive any special treatment.
+ specific compatible string is a "multiboot,kernel".
+
+ Xen will check all the modules for the XSM Magic from the second
+ module that lacks a specific compatible string. According to the
+ result of the detection:
+ - if it's a XSM, Xen will assume its compatible string is a
+ "xen,xsm-policy";
+ - if it's not a XSM, for the second module that lacks a specific
+ compatible string, Xen will assume its compatible string is a
+ "multiboot,ramdisk"; for the third and subsequent modules those
+ lacks a specific compatible string will not receive any special
+ treatment.
+ This means if the ramdisk module is present and does not have the
+ compatible string "multiboot,ramdisk", then it must always be the
+ second module.
+ Note: This XSM Magic detection behavior was introduced by Xen 4.7.
+ Xen 4.6 (and downwards) still requires the XSM module to have the
+ compatible string "xen,xsm-policy".
Xen 4.4 supported a different set of legacy compatible strings
which remain supported such that systems supporting both 4.4
--
2.5.5
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-04-21 11:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 11:07 fu.wei [this message]
2016-04-21 11:40 ` [PATCH v2] docs/arm64: update the documention for loading XSM support Jan Beulich
2016-04-26 14:00 ` Fu Wei
2016-04-22 16:40 ` Julien Grall
2016-04-22 16:41 ` Julien Grall
2016-04-22 16:43 ` Wei Liu
2016-04-22 17:28 ` Stefano Stabellini
2016-04-22 17:37 ` Ian Jackson
2016-04-22 17:29 ` [PATCH v3] " Ian Jackson
2016-04-22 17:37 ` Konrad Rzeszutek Wilk
2016-04-25 9:42 ` Julien Grall
2016-04-25 15:12 ` Ian Jackson
2016-04-25 15:25 ` Stefano Stabellini
2016-04-25 15:35 ` [PATCH] docs/arm64: clarify " Ian Jackson
2016-04-25 16:16 ` Julien Grall
2016-04-25 16:35 ` Ian Jackson
2016-04-25 16:38 ` [PATCH v2] " Ian Jackson
2016-04-25 16:45 ` Julien Grall
2016-04-25 16:49 ` Wei Liu
2016-04-26 9:47 ` [PATCH] " Stefano Stabellini
2016-04-26 9:56 ` Wei Liu
2016-04-26 9:57 ` Stefano Stabellini
2016-04-26 14:03 ` [PATCH v3] docs/arm64: update " Fu Wei
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=1461236829-11491-1-git-send-email-fu.wei@linaro.org \
--to=fu.wei@linaro.org \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jcm@redhat.com \
--cc=julien.grall@arm.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=leif.lindholm@linaro.org \
--cc=linaro-uefi@lists.linaro.org \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-devel@lists.xensource.com \
/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).