[roll] Roll fuchsia [kernel][hypervisor][arm64] Route SError exceptions to EL2

On ARM64, asynchronous SError (system error) exceptions are triggered
external to the CPU, such as a memory access which has passed all the
MMU checks but encounters an error on the memory bus.

The Zircon kernel currently masks SErrors (https://fxbug.dev/72659,
https://fxbug.dev/75834), but Linux guest kernels keep them unmasked.
The result is that if host Zircon encounters an SError exception, it
will remain pending until Zircon finally schedules a Linux guest, which
will spuriously take the exception.

This CL updates the hypervisor's EL2 config to route SErrors taken by
guests to EL2. These are sent to the host Zircon kernel which prints an
error message to the kernel log, and then resumes the guest.

Original-Bug: 57651
Original-Fixed: 75609

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/565622
Original-Revision: 9e6aecfedfeace7b2c788bf395cb1b49fd47f356
GitOrigin-RevId: 1be335d0cb8d9fb3fd108f5d1bfde7e1b90e2f01
Change-Id: I939fc4f3dbf376960e2d4f96ff435b1fdd0111fa
1 file changed
tree: d80e2e1b2997beb482ed37be598c59100583d5a0
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.