From: Julien Grall <julien.grall@arm.com>
To: xen-devel@lists.xen.org
Cc: Julien Grall <julien.grall@arm.com>, sstabellini@kernel.org
Subject: [PATCH v4 12/15] xen/arm: Document the errata implemented in Xen
Date: Wed, 22 Jun 2016 12:15:27 +0100 [thread overview]
Message-ID: <1466594130-19251-13-git-send-email-julien.grall@arm.com> (raw)
In-Reply-To: <1466594130-19251-1-git-send-email-julien.grall@arm.com>
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 <julien.grall@arm.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
---
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 |
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-22 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 11:15 [PATCH v4 00/15] xen/arm: Introduce alternative runtime patching for ARM64 Julien Grall
2016-06-22 11:15 ` [PATCH v4 01/15] xen/arm: Makefile: Sort the entries alphabetically Julien Grall
2016-06-22 11:15 ` [PATCH v4 02/15] xen/arm: Include the header asm-arm/system.h in asm-arm/page.h Julien Grall
2016-06-22 11:15 ` [PATCH v4 03/15] xen/arm: Add macros to handle the MIDR Julien Grall
2016-06-22 11:15 ` [PATCH v4 04/15] xen/arm: Add cpu_hwcap bitmap Julien Grall
2016-06-22 11:15 ` [PATCH v4 05/15] xen/arm64: Add an helper to invalidate all instruction caches Julien Grall
2016-06-22 11:15 ` [PATCH v4 06/15] xen/arm: arm64: Move the define BRK_BUG_FRAME into a separate header Julien Grall
2016-06-22 11:15 ` [PATCH v4 07/15] xen/arm: arm64: Reserve a brk immediate to fault on purpose Julien Grall
2016-06-22 11:15 ` [PATCH v4 08/15] xen/arm: arm64: Add helpers to decode and encode branch instructions Julien Grall
2016-06-22 11:15 ` [PATCH v4 09/15] xen/arm: Introduce alternative runtime patching Julien Grall
2016-06-22 11:15 ` [PATCH v4 10/15] xen/arm: cpufeature: Provide an helper to check if a capability is supported Julien Grall
2016-06-22 11:15 ` [PATCH v4 11/15] xen/arm: Detect silicon revision and set cap bits accordingly Julien Grall
2016-06-22 11:15 ` Julien Grall [this message]
2016-06-22 11:15 ` [PATCH v4 13/15] xen/arm: arm64: Add Cortex-A53 cache errata workaround Julien Grall
2016-06-22 11:15 ` [PATCH v4 14/15] xen/arm: arm64: Add cortex-A57 erratum 832075 workaround Julien Grall
2016-06-22 11:15 ` [PATCH v4 15/15] xen/arm: traps: Don't inject a fault if the translation VA -> IPA fails Julien Grall
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=1466594130-19251-13-git-send-email-julien.grall@arm.com \
--to=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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).