commit | 04724ae70ef722ad100a971c0585ed82903a0c57 | [log] [tgz] |
---|---|---|
author | Venkatesh Srinivas <venkateshs@google.com> | Fri Jan 25 20:39:55 2019 +0000 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 29 02:43:05 2019 +0000 |
tree | c61adf5a7ac37c04a722b3a92395ca58b10aefe1 | |
parent | ebaf2460c873d081f47daa24e20414af86b7a3ab [diff] |
[virtio] scsi: Correct loop conditions for target/LUN scan 1) Remove support for scanning non-zero channels. virtio-scsi's config space has a field for 'max_channels', but the device can only encode channel 0 targets. Remove the max_channel loop since we can't use non-zero channels. 2) Use <= (rather than <) for max_target/max_lun comparison. QEMU and GCE's hypervisor disagree on the definition of the max_target and max_lun fields. The virtio spec is ambiguous as to which definition is correct. Use <= conservatively to not skip targets. ZX-2314 Tested: 1) QEMU: finds target 0:1:1 ./scripts/run-zircon-x64 -- -drive if=none,id=hd,file=/tmp/blk.img \ -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd,scsi-id=1,lun=1 2) GCE -- finds target 1:0. Change-Id: I684d67b8fc7449c72b14290ce88f226e00def672
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.