From patchwork Wed Jun 22 11:15:27 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Julien Grall X-Patchwork-Id: 70635 Delivered-To: patch@linaro.org Received: by 10.140.28.4 with SMTP id 4csp2492751qgy; Wed, 22 Jun 2016 04:17:58 -0700 (PDT) X-Received: by 10.237.51.98 with SMTP id u89mr36135304qtd.71.1466594269459; Wed, 22 Jun 2016 04:17:49 -0700 (PDT) Return-Path: Received: from lists.xenproject.org (lists.xenproject.org. [192.237.175.120]) by mx.google.com with ESMTPS id s20si5602542qks.271.2016.06.22.04.17.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jun 2016 04:17:49 -0700 (PDT) Received-SPF: neutral (google.com: 192.237.175.120 is neither permitted nor denied by best guess record for domain of xen-devel-bounces@lists.xen.org) client-ip=192.237.175.120; Authentication-Results: mx.google.com; spf=neutral (google.com: 192.237.175.120 is neither permitted nor denied by best guess record for domain of xen-devel-bounces@lists.xen.org) smtp.mailfrom=xen-devel-bounces@lists.xen.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bFg8O-0002U1-HC; Wed, 22 Jun 2016 11:15:52 +0000 Received: from mail6.bemta6.messagelabs.com ([85.158.143.247]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bFg8N-0002El-1t for xen-devel@lists.xen.org; Wed, 22 Jun 2016 11:15:51 +0000 Received: from [85.158.143.35] by server-2.bemta-6.messagelabs.com id 53/63-11548-6637A675; Wed, 22 Jun 2016 11:15:50 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRWlGSWpSXmKPExsVysyfVTTetOCv c4P4lEYslHxezODB6HN39mymAMYo1My8pvyKBNWPVhzOsBe+kKjY+/cvYwLhctIuRi0NIYBOj xLYF19khnNOMEg/e7WPqYuTkYBPQlLjz+ROYLSIgLXHt82VGEJtZwEHizcd7LCC2sICnxNyz0 8BqWARUJVoW3mIHsXkFXCX2/N/KBmJLCMhJnDw2mRXE5gSKnzw6GWyOkICLxO0De1gnMHIvYG RYxahenFpUllqka6yXVJSZnlGSm5iZo2toYKaXm1pcnJiempOYVKyXnJ+7iRHoXwYg2MHY8c/ pEKMkB5OSKK+8cla4EF9SfkplRmJxRnxRaU5q8SFGGQ4OJQne/iKgnGBRanpqRVpmDjDQYNIS HDxKIrx1IGne4oLE3OLMdIjUKUZFKXGIPgGQREZpHlwbLLgvMcpKCfMyAh0ixFOQWpSbWYIq/ 4pRnINRSZg3CGQKT2ZeCdz0V0CLmYAWL+tPB1lckoiQkmpgVL1vISB39ObPEzE/a/5NOXfE6f 3WK7+95l7YuubMQsZw268hB0QmFU5gPevNuZZfunkfw/6ZvlcquDwKtyX2x1+6XWmlbNh+4Ob P37yiB78H/K6+cFnDtCxHm7VFu2lDles+1ztbj5tHrY17NltodTPT6WdmVg0lMerFFcs1ffNm M0ZcaW8uVGIpzkg01GIuKk4EANmUbgNpAgAA X-Env-Sender: julien.grall@arm.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1466594149!20120750!1 X-Originating-IP: [217.140.101.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 8.46; banners=-,-,- X-VirusChecked: Checked Received: (qmail 62462 invoked from network); 22 Jun 2016 11:15:50 -0000 Received: from foss.arm.com (HELO foss.arm.com) (217.140.101.70) by server-10.tower-21.messagelabs.com with SMTP; 22 Jun 2016 11:15:50 -0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 70B803B0; Wed, 22 Jun 2016 04:16:35 -0700 (PDT) Received: from e108454-lin.cambridge.arm.com (e108454-lin.cambridge.arm.com [10.1.215.28]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D83E33F213; Wed, 22 Jun 2016 04:15:47 -0700 (PDT) From: Julien Grall To: xen-devel@lists.xen.org Date: Wed, 22 Jun 2016 12:15:27 +0100 Message-Id: <1466594130-19251-13-git-send-email-julien.grall@arm.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1466594130-19251-1-git-send-email-julien.grall@arm.com> References: <1466594130-19251-1-git-send-email-julien.grall@arm.com> Cc: Julien Grall , sstabellini@kernel.org Subject: [Xen-devel] [PATCH v4 12/15] xen/arm: Document the errata implemented in Xen 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: , MIME-Version: 1.0 Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" The new document will help to keep track of each erratum Xen is able to handle. The text is based on the Linux doc in Documents/arm64/silicon-errata.txt. Also list the current errata that Xen is aware of. Signed-off-by: Julien Grall Acked-by: Stefano Stabellini --- Changes in v4: - Fix grammar in the document : s/by ARM64/on ARM64/ - Add Stefano's acked-by Changes in v3: - Fix grammar in the commit message - s/Linux/Xen/ - Mention that runtime patching is only supported by ARM64 --- docs/misc/arm/silicon-errata.txt | 45 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 docs/misc/arm/silicon-errata.txt diff --git a/docs/misc/arm/silicon-errata.txt b/docs/misc/arm/silicon-errata.txt new file mode 100644 index 0000000..5d54694 --- /dev/null +++ b/docs/misc/arm/silicon-errata.txt @@ -0,0 +1,45 @@ + Silicon Errata and Software Workarounds + ======================================= + +It is an unfortunate fact of life that hardware is often produced with +so-called "errata", which can cause it to deviate from the architecture +under specific circumstances. For hardware produced by ARM, these +errata are broadly classified into the following categories: + + Category A: A critical error without a viable workaround. + Category B: A significant or critical error with an acceptable + workaround. + Category C: A minor error that is not expected to occur under normal + operation. + +For more information, consult one of the "Software Developers Errata +Notice" documents available on infocenter.arm.com (registration +required). + +As far as Xen is concerned, Category B errata may require some special +treatment in the hypervisor. For example, avoiding a particular sequence +of code, or configuring the processor in a particular way. A less common +situation may require similar actions in order to declassify a Category A +erratum into a Category C erratum. These are collectively known as +"software workarounds" and are only required in the minority of cases +(e.g. those cases that both require a non-secure workaround *and* can +be triggered by Xen). + +For software workarounds that may adversely impact systems unaffected by +the erratum in question, a Kconfig entry is added under "ARM errata +workarounds via the alternatives framework". These are enabled by default +and patched in at runtime when an affected CPU is detected. Note that +runtime patching is only supported on ARM64. For less-intrusive workarounds, +a Kconfig option is not available and the code is structured (preferably +with a comment) in such a way that the erratum will not be hit. + +This approach can make it slightly onerous to determine exactly which +errata are worked around in an arbitrary hypervisor source tree, so this +file acts as a registry of software workarounds in the Xen hypervisor and +will be updated when new workarounds are committed and backported to +stable hypervisors. + +| Implementor | Component | Erratum ID | Kconfig | ++----------------+-----------------+-----------------+-------------------------+ +| ARM | Cortex-A15 | #766422 | N/A | +| ARM | Cortex-A57 | #852523 | N/A |