[roll] Roll fuchsia [kernel][efi] Do not map EFI runtime MMIO as executable This fixes the associated bug where as a result of an MMIO region being marked as executable, the VM tried to perform data cache operations on it needed for icache consistency, which is invalid for MMIO. In particular, we update the logic for mapping EFI memory descriptor attributes to MMU flags to assume that double-negatives apply sensibly: "not read-only" implies writable and "not execute-protected" implies executable. Original-Fixed: 418237434 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1279376 Original-Revision: e6a66e05b0ba1cc3d50530ac6185949ec581e68d GitOrigin-RevId: ffaf778c78dbfd06500ad9a0ce43f8fc4222f4e2 Change-Id: I7963fd6ab50edd9072476ce0c5d209baeabe5e46
This repository contains Fuchsia's Global Integration manifest files.
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 in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.