[roll] Roll fuchsia [kernel][vm] Forbid cache ops on phys VMOs

Physical VMOs are explicitly created from non-RAM areas, which are
protected / unmapped from the physmap, making the cache operations
non-sensical at best and erroneous at worst.

As per RFC-0252 this makes the operation an error and updates the
documentation.

This is a reland of Ic7b37bda88bbafada330a4ce415577928ec81a4d now
that the failing sysmem logic and tests have been updated to avoid
performing cache operations on physical VMOs.

Run-All-Tests: True
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1097312
Original-Revision: ecb22c92e89ed6dc426aaa01f77f3d9fab78ea90
GitOrigin-RevId: bbae8c6cc104560997bacfae68f420bda190f207
Change-Id: I421793803a0f5cfb2ca70013812b4f3152a1264e
1 file changed
tree: 7357a2cf48324c115b6f6f9541b2e9cdd90b7e3c
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
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.