diff mbox series

[Xen-devel,for-4.13,v4,01/19] docs/misc: xen-command-line: Remove wrong statement from serrors=diverse

Message ID 20191031150922.22938-2-julien.grall@arm.com
State New
Headers show
Series xen/arm: XSA-201 and XSA-263 fixes | expand

Commit Message

Julien Grall Oct. 31, 2019, 3:09 p.m. UTC 
When serrors=diverse is selected by the user, we will only synchronize
the pending SErrors on entry to hypervisor from guest context and exit
from guest to hypervisor context.

We don't need synchronize SErrors between guest context switch as they
would be categorized to Hypervisor generated SErrors in any case.

Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>

---
    The documentation for the option serrors will be fully reworked in a
    follow-up patch. But the dsb/isb in the context switch will be
    removed before the documentation rework. So to avoid any question
    while reviewing the next patch, drop it now.

    Changes in v3:
        - Add Stefano's reviewed-by

    Changes in v2:
        - Patch added
---
 docs/misc/xen-command-line.pandoc | 1 -
 1 file changed, 1 deletion(-)
diff mbox series

Patch

diff --git a/docs/misc/xen-command-line.pandoc b/docs/misc/xen-command-line.pandoc
index ef56defef5..30a04df4db 100644
--- a/docs/misc/xen-command-line.pandoc
+++ b/docs/misc/xen-command-line.pandoc
@@ -1877,7 +1877,6 @@  hypervisors handle SErrors:
   1. dsb/isb on all EL1 -> EL2 trap entries to categorize SErrors correctly.
   2. dsb/isb on EL2 -> EL1 return paths to prevent slipping hypervisor
      SErrors to guests.
-  3. dsb/isb in context switch to isolate SErrors between 2 vCPUs.
 
 * `forward`:
   The hypervisor will not distinguish guest SErrors from hypervisor SErrors.