From patchwork Fri Apr 22 17:29:34 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ian Jackson X-Patchwork-Id: 8914671 Return-Path: X-Original-To: patchwork-xen-devel@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork1.web.kernel.org (Postfix) with ESMTP id 863109F372 for ; Fri, 22 Apr 2016 17:31:27 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 9D7F3201C8 for ; Fri, 22 Apr 2016 17:31:26 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B2890201C0 for ; Fri, 22 Apr 2016 17:31:25 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ateth-0005WR-Ng; Fri, 22 Apr 2016 17:29:41 +0000 Received: from mail6.bemta6.messagelabs.com ([85.158.143.247]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1atetg-0005Ux-9I for xen-devel@lists.xen.org; Fri, 22 Apr 2016 17:29:40 +0000 Received: from [85.158.143.35] by server-2.bemta-6.messagelabs.com id E1/92-09532-38F5A175; Fri, 22 Apr 2016 17:29:39 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFIsWRWlGSWpSXmKPExsXitHRDpG5zvFS 4wcS9bBZLPi5mcWD0OLr7N1MAYxRrZl5SfkUCa8aG+x+YC9aIV8x+/J+5gXGhcBcjJ4eEgL/E hK4rLCA2m4CuxKVpE5lBbF4BQYmTM5+AxZkFdCQW7P7EBmHLS2x/Oweqxl7izp/pYDUsAqoSf 4+uZgKxRQTUJf5cmMDYxcgFVL+bSeLMxqfsIAlhAT+JU5tWgdmcQEUbps8BaxASiJX4ePMZM8 RBxhKr738EGsoBFFeTmLs+HiLMLXH79FTmCYz8s5CcNwvJebOQnLeAkXkVo3pxalFZapGukV5 SUWZ6RkluYmaOrqGBmV5uanFxYnpqTmJSsV5yfu4mRmAIMgDBDsZlf50OMUpyMCmJ8nqFSIUL 8SXlp1RmJBZnxBeV5qQWH2LU4+AQOLfn7jFGgb7PExYxSbHk5eelKknwLogDqhYsSk1PrUjLz AFGDEyDBAePkgjvv1igNG9xQWJucWY6ROoUo6KUOO9qkD4BkERGaR5cGyxKLzHKSgnzMgKdJs RTkFqUm1mCKv+KUZyDUUmYdwvIFJ7MvBK46a+AFjOBLL4gCbK4JBEhJdXAyL/0dFmEQ9kEZ4E aFu0pnwLMip8oW2z57Jle3/RGvp330IcLd1UeMvG7nl/rkLkqh1PUK3K2M2vPRLn9rFuL0u9E Ftpt/3TaWqnjLaehgvFmm7pVnCuOp57pZw7juf1hm5pu58YfUXMvTuyf9n3xRzV/58pdRX429 7Z9jmNM0GYV/smwKydbiaU4I9FQi7moOBEAUxD0LM0CAAA= X-Env-Sender: prvs=91335fb6d=Ian.Jackson@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1461346177!10941592!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 8.34; banners=-,-,- X-VirusChecked: Checked Received: (qmail 64752 invoked from network); 22 Apr 2016 17:29:38 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Apr 2016 17:29:38 -0000 X-IronPort-AV: E=Sophos;i="5.24,518,1454976000"; d="scan'208";a="349087982" From: Ian Jackson MIME-Version: 1.0 Message-ID: <22298.24446.56007.535207@mariner.uk.xensource.com> Date: Fri, 22 Apr 2016 18:29:34 +0100 To: Julien Grall In-Reply-To: <571A53E2.2020603@arm.com> References: <1461236829-11491-1-git-send-email-fu.wei@linaro.org> <571A53E2.2020603@arm.com> X-Mailer: VM 8.1.0 under 23.4.1 (i486-pc-linux-gnu) X-DLP: MIA2 Cc: xen-devel@lists.xensource.com, Wei Liu , jcm@redhat.com, George Dunlap , leif.lindholm@linaro.org, xen-devel@lists.xen.org, sstabellini@kernel.org, linaro-uefi@lists.linaro.org, dgdegra@tycho.nsa.gov, fu.wei@linaro.org Subject: [Xen-devel] [PATCH v3] docs/arm64: update the documention for loading XSM support X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_MED, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Julien Grall writes ("Re: [PATCH v2] docs/arm64: update the documention for loading XSM support"): > The new version looks good to me: > Acked-by: Julien Grall > > Can a native speaker (Ian, Konrad, George) double-check the wording)? I found it rather difficult to read. See updated version, attached. I dropped your ack because I want to be sure that the new version still describes the actual behaviour. I kept Wei's release-ack. Thanks, Ian. From bd8f24667d353a4c90203d51c1fdb42a66b79973 Mon Sep 17 00:00:00 2001 From: Fu Wei Date: Thu, 21 Apr 2016 19:07:09 +0800 Subject: [PATCH] docs/arm64: update the documention for loading XSM support This patch updates the documentation for allowing detection of an XSM module that lacks a specific compatible string. (This mechanism was added in commit ca32012341f3, "xen/arm64: check XSM Magic from the second unknown module.") Signed-off-by: Fu Wei Signed-off-by: Ian Jackson Release-acked-by: Wei Liu Reviewed-by: Konrad Rzeszutek Wilk --- docs/misc/arm/device-tree/booting.txt | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/docs/misc/arm/device-tree/booting.txt b/docs/misc/arm/device-tree/booting.txt index ad98bf3..f3179d6 100644 --- a/docs/misc/arm/device-tree/booting.txt +++ b/docs/misc/arm/device-tree/booting.txt @@ -24,10 +24,29 @@ 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 examine each module, starting from the second + module that lacks a specific compatible string. Xen will + check each such module for the XSM Magic number: + + - For a module which has the XSM Magic number: it will be + treated by Xen as if its compatible string was + "xen,xsm-policy"; + + - For a module which does not have the XSM Magic: the second + module lacking a compatible string will be treated by Xen as + if its compatible string was "multiboot,ramdisk"; for the + third and subsequent modules which lack a specific + compatible string, Xen will not apply 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