[roll] Roll fuchsia [kernel][vm] Optimize protect ranges

Optimizes the protection of ranges by taking into account the previous
arch mmu flags for each range being modified. Knowing the previous
flags lets us skip manipulating the arch aspace in some circumstances
where we know it would be redundant.

In particular, without knowing the previous permissions if the new
permissions had WRITE, we would have to protect to the new permissions
minus WRITE, even if the new permissions were the same as the old ones.
Now this scenario can be identified and skipped.

Original-Bug: 90014
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/622424
Original-Revision: d97c05d2301799ed585620a9c5c739d36e7b5d3d
GitOrigin-RevId: c0f8c7ef78a16ee7b5226d7cdb61fbb6e0d9fda0
Change-Id: I4c9021c91269e8e73a9accbf9ad0532ddfb03a5f
1 file changed
tree: c6a67e37fdeefcb7a79328d0e19bcba15cd2182a
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. 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.