[roll] Roll fuchsia [kernel][riscv64] Fill in and stub out arch-specific hooks

This fills in most of the missing files, types, and functions for
riscv64.  Most are just stubbed out, but some have implementations
of the first best guess at what they might partially look like.

It introduces the `kernel_no_userabi` GN build argument, which
when left to default will be false in the riscv64 kernel toolchain
for now. This omits all the syscall, vDSO, and userboot code so
there is no user-space support at all. Users are a myth.

This is enough to get all the kernel code compiling, with lots of
undefined symbols at link time.  Since it fails at link time, the
riscv64 kernel build is not attempted even with the GN build
argument `all_cpu_phys_boot_tests=true`.  An easy way to just
attempt the kernel build is to add this like to args.gn:
universe_package_labels += ["//zircon/kernel(//zircon/kernel:kernel_riscv64)"]

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/806290
Original-Revision: f8c925da99af22fa9da80baa25c508bdaede8895
GitOrigin-RevId: f0d4e99aff4da27f6b80bd731c7b3c749241fd62
Change-Id: Id20192bc48a81486b9775c6983cb078c14241d92
1 file changed
tree: 62511824fe1ad51be22d39e5a1705206a53ef094
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.