xen/arm: traps: Rework __do_serror() documentation
authorJulien Grall <julien.grall@arm.com>
Thu, 31 Oct 2019 15:09:06 +0000 (15:09 +0000)
committerJulien Grall <julien.grall@arm.com>
Fri, 1 Nov 2019 13:57:07 +0000 (13:57 +0000)
commitae2f94ca67035ee2cd769deed48e4832328d41ba
tree66571d109795a34960a9d88e3f771c5cf413d6c8
parentabb234b5acc5380fc85388c7d98e79533b4eef95
xen/arm: traps: Rework __do_serror() documentation

The documentation on top of __do_serror() is trying to describe all the
possibilities to receive an SErrors.

The description of type#2 is quite misleading because receiving an
SError in EL2 after unmasking SError interrupt ({PSTATE, CPSR}.A) does
not necessarily imply the SError were generated by the guest. You also
need to be in a special window (see abort_guest_exist_{guest, end}).

However, for the context of the function it does not matter how we
categorize the interrupts. What matter is to know whether this is a
guest-generated SError.

All the documentation of __do_serror() is now reworked to avoid
misleading information.

Take the opportunity to simplify the code after the forward option has
been dropped.

Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
Release-acked-by: Juergen Gross <jgross@suse.com>
xen/arch/arm/traps.c