| commit | 8e9c6a63b39399c99794ef22c607b050ef558ee5 | [log] [tgz] |
|---|---|---|
| author | Venkatesh Srinivas <venkateshs@google.com> | Mon Jan 28 17:34:41 2019 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 29 01:32:51 2019 +0000 |
| tree | 0b8ad8262b8294e22ba0abc9d289e4844077acba | |
| parent | 3c6829009ec5978d63b78060ca8e4e08c4e75a6b [diff] |
[virtio] scsi: Fix encoding of LUNs virtio-scsi requires Target/LUN pairs be encoded into an 8-byte buffer in a particular format -- 1. First byte set to 1 2. Second byte set to target 3. Third and fourth byte representing a 'single level LUN structure' Per the SCSI Architecture Manual, the single-level format we should be using is the flat addressing method (table 6, SAM-3 T10/02-119r0) or (tabel 9, Flat space addressing, SAM-3 T10/02-119r0). Bits 7-6 of the low byte should be '01'. Then we should pack the 6 MSBs of the LUN into the low byte and the 8 LSBs into the high byte. The prior version of this code did not set the address method (implicit Peripheral device address method) and incorrectly mashed the LUN for that mode. ZX-2314 Tested: With the correct loop condition CR, booted on GCE and QEMU. Tested that expected LUNs were found and bound to virtio.so Change-Id: I6b4a53ea16dec0962233d143660744edd012dfc8
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
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.