| commit | 0a6ed94c347caf028dda307e5d08e150399c2eb3 | [log] [tgz] |
|---|---|---|
| author | Muralidhar.S.R <muralidhar.s.r@huawei.com> | Mon Nov 05 13:07:58 2018 +0530 |
| committer | Mike Voydanoff <voydanoff@google.com> | Fri Nov 23 10:35:34 2018 -0800 |
| tree | 1abf7e823ce570957b0c4d909e2f031d63d709a8 | |
| parent | 7dd8f7698d45a8d2ccad9daccca63404d072869d [diff] |
[arm][mm] Move ASID from TTBR0_EL1 to TTBR1_EL1 When mapping kernelspace and userspace with different ASIDs, check if tcr_el1 is not getting updated (ie; set to 0) In this case, move the ASID to TTBR1 else, this will result in an invalid mapping Test: Tested on kirin970 and hikey960 board. Device booted to shell Change-Id: I8ac56a75fbedcfc43b9b0e0b912447201ea6ed70
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.