Test: fit-test
Change-Id: I9b20208689f55a4835f02093ee49abd4666782cc

Reland of 7baf23bc with build fix

Test: fit-test
Change-Id: I02296cd441cd999268c1f686d334ef98f7e02eee

After this CL, all the FDIO objects that use a ZXIO backend use the same
memory layout. This CL prepares us for unifying the ZXIO-based FDIO
objects.

Test: No behavior change
Change-Id: I2568eb3034bcea06804c37e10e40e0b7de704b7a

All clients have been migrated to zx_socket_shutdown.

ZX-2994 #done
Test: Removing dead code
Change-Id: I6240cd9c446aa49c5bbc36b42f0fbafd8ac7f707

This reverts commit 7baf23bc.

Reason for revert: blocking Zircon roll
...
sequencer.h:47:14: error: use of class template 'fit::bridge' requires template arguments
...

Original change's description:
> [fit] Add fit::sequencer for ensuring sequential execution order.
> 
> Test: fit-test
> Change-Id: I2f44bdba931f8a7bb9a0917549c1eb7c43858b70

TBR=jeffbrown@google.com,thatguy@google.com

Change-Id: I30bc48691e32dca236a0164f002135d46f8d4690
No-Presubmit: true
No-Tree-Checks: true
No-Try: true

Test: This adds a test.
Change-Id: I4c380678301bf724c95693c538d2c97ad48567df

Revert "[fit] Rename sequential_executor to single_threaded_executor."
Revert "[fit] Add fit::sequencer for ensuring sequential execution order."

This reverts commit abf79d33.
This reverts commit 7baf23bc.

This code does not build, at least as C++14:

In file included from headers/headers.cc:98:
.../pkg/fit/_virtual_includes/fit/lib/fit/sequencer.h:47:14: error: use
of class template 'fit::bridge' requires template arguments
        fit::bridge bridge;

Test: Failed SDK builders
Change-Id: I95ff20ee448faea541ce7526ad139bbaf9449809

In order to reduce verbosity in the output of k counters, instead of
always printing both the sum and the per-core count, only output the sum
unless:

1) the user specifies a new -v option as in e.g.
   `k counters view -v kernel.channel.messages`

2) there's a outlier in the per-core counts that might be indicate that
   one core is working unusually hard. This outlier calculation used is
   https://en.wikipedia.org/wiki/Outlier#Tukey's_fences with k=1.5,
   which is not perfect. It is fairly conservative and might still
   output in not-so-interesting cases.

ZX-3008 #comment

Test: New unittest counters_tests added, quartile calc manually compared to https://docs.google.com/spreadsheets/d/1D58chwOpO-3_c41NMGJkpmFuOpGSYH-W50bD6MdOAjo/edit?usp=sharing
Change-Id: I2ec5fcdb0d5320abf70fc5cea7785b380d90c29b

Update symbolizer to revision 7140d924a314402c36bae66f34d0e77587ffb825

Test: CQ
Change-Id: I323ad5af628ccfbce59d3cd4c4861f3b8f45a66f

The new name does a better job conveying the behavior of the executor
and is less ambiguous particularly in the presence of the newly
introduced fit::sequencer which really does apply sequencing.

Test: fit-test
Change-Id: I7d4375fd340c929658652f1b7e8bfc1167676b52

Test: fit-test
Change-Id: I2f44bdba931f8a7bb9a0917549c1eb7c43858b70

TEST: install-disk-image-test passes, paving mt8167s starting to work

Change-Id: I804614df6c771fec739f735b3e331da9c5b64a78

Test: No behavior change
Change-Id: If6d8c2c215208765d2687712ac39b00a08d14560

This bootstraps the required devices to enable communication with the
bcm43458 wifi/bluetooth transceiver chip.

Test: wlan scan+connect; ping w/eth0 disconnected
Change-Id: I948bf41df1058dd93e77dea7036e9b3b4f6fb668

The pci bus driver will now obtain platform information from
pciroot and map an ecam into its address space if one exists.

Test: Checked config dump of 00:00.0, and verified kpci behavior
has not regressed;

Change-Id: I50c393c543de0323671b623c4deebe445305b727

These symbols are unused.

Test: No behavior change
Change-Id: I643a6b7633a1ca5dbf824403ee7773947ee1d6a2

As far as I can tell these haven't been used in well over a year.

Test: Booted
Change-Id: I7c713a1d565011617d193647fb9704201a614ac1

We no longer need this header.

Test: No behavior change
Change-Id: I03679671db7c478709c0f78f815c310cb238b3c5

Test: build/ran kpci with graphics under qemu

Change-Id: I87a256ccc299f11cd1fd4aa4667a9acf89d364b7

This CL removes declarations from remoteio.h that are redundant with
declarations in io.fidl.

Test: No behavior change
Change-Id: Id23f270b69b575b104bf00c2bed0140c6408fff0

XRay needs to retrieve the innermost VMAR to allow changing its
permissions when patching function entry and exit points. This is
currently not possible since the dynamic linker always closes the VMAR
handle. To support XRay, when the dynamic linker is being built for
XRay, we don't close the VMAR handle and provide a new runtime function
__sanitizer_change_code_protection which allows caller to change the
protection of its own code segment.

Test: manual
Change-Id: If6a780d29cce389068574cc8b50d0f2387f8e3a3

TEST: install-device-partitioner-test
Change-Id: I8be7223ca9d3721c93728552290d5e16cf41cc24

This will allow the user to receive fewer callbacks for
isochronous transfers.

Implementation will be in next CL.

Also removes old cb_on_error_only implementation, which had
issues detailed in ZX-932.

An example of how the user would call the API:
https://fuchsia-review.googlesource.com/c/garnet/+/227672

ZX-932 #comment

TEST= set_root_view video_display, does not affect current video implementation

Change-Id: Ia06c8a6ebccd1042e667a9e2d623c3b57265a1ff

test: dictionary
Change-Id: I92f2bea38b9897f91c20b07ed6f535a02ed2b7ec

In an error handling case, zx_task_resume() was still being used. It's
deprecated and to-be-removed shortly, so switch to the newer function.

ZX-2720 #comment

Test: CQ
Change-Id: I49d2b0050bb8edec93fe9de644c157e294d0c4b2

Paring down the number of references to this so that it can actually be
removed.

ZX-2720 #comment

Test: CQ
Change-Id: Ibb0d91809f5914bde27a0bef3a76022ed31ac6a1

DX-636 #comment

TESTED=`crasher` on x64 and arm64

Change-Id: I5f9a9ace2f2cf066e50c5d3960e597658508651e

The only non-test user of either count was just using the commit count
to verify that the whole range was committed, which is redundant with
the commit being successful.

Test: k ut, core-tests
Change-Id: I51ba403c5f1711c99108a538682b098bb6f140fd

This library was based off of the code that was previously being used.

Test: Booted with this change
Change-Id: I2115e2f6350d59e34e1b5f361c4717f597abf938

This is an implmentation of FTP-020.  The next step will be to deprecate and remove
ordinals from existing FIDL files.

To make removal easier, this CL introduces a --remove-ordinals flag to fidl-format.

Test: Unittests added for compiler and formatter.
Change-Id: Id5c10f84bde95656fca3368a4fb21ca00310197b

This code will soon be shared by the new bootsvc and by fshost.

ZX-3027 #comment Lift bootfs parser into shared code

Test: Added test suite.  ZX-3034 is a bug for making even more thorough
tests.

Change-Id: I583130ced2675d1471d86e3a51ec93c7f28f5bfe

This makes more syscall pages link to `object_wait_async`
when they already link to the other wait calls.

TEST: No behavior change
Change-Id: I8770a9baf9ab5aea0e00719f9f7f262994ddc795

NET-1915 #comment

Test=n/a

Change-Id: Id1c5a9bb56059ce92880df1b9789c1d45b437daf

there doesn't seem to be a self_dump_func or an actual use of
crashed_thread

TESTED=`crasher` on x64 and arm64

Change-Id: Ib5c676fea8fc40679a894d4665b29490a0784497

Currently, there is only 1 list_node_t pointer in usb_request_t and
differnt drivers in the usb stack that track a usb request enqueue it
using this node. This will lead to bugs where the request is simultaneously
included in multiple lists changing the next and previous pointers of the node.
This changeset makes use of the xhci's private list_node_t pointer
that is only used in xhci driver. In xhci, a particular request is first
queued in queued_reqs, then moved to pending_reqs. At a particular
time,it is part of only one list.

Test:
vim2: -fx serve; plugged in a mass storage device.
      - lsusb; iochk
pixelbook: -fx serve using usb ethernet adapter
           -plug in a usb mass storage device.
           -lsusb; iochk.
           -audio info using a usb audio headset.
astro: - fx netboot; lsusb; Made sure the usb ethernet adapter showed up.

Change-Id: I172e36046366b41d8e9cc1bd5a50ba4264618475

This CL adds basic fuzzers for the lz4 library.

There are two fuzzers being added. Once is a "roundtrip" fuzzer, that
will try to compress the input data, decompress the result, and check
that they are equal. The other fuzzer just tries to decompress random
data and crashes right away (until we fix it).

TEST=`fx fuzz start lz4.{fuzzname}` in a pixelbook running fuchsia.

Change-Id: Ic3b9ab98e3c8cb1d345605ad3b0b667dac8b8c5f

This adds the framework for a userspace PCI driver using
DDKTL. PciConfig has been ported from the kernel bus driver
and proxying config access to the pciroot protocol has been
implemented.

Test: Confirmed the output of the root 00:00.0 device config
space dump, and ensured kernel pci behavior remains unchanged.

Change-Id: Ic7ec3dc72ce2ff34196ff624234127937383459c

This CL adds a zxio backend for vmofile but does not migrate the
production codepath to zxio.

Test: vmofile-test.cpp
Change-Id: I84721065540d304d257269a8527eb1e7a7926182

Currently in sdmmc_bind function, we always create a block device. Later
we probe the device and once we know its a sdio device we remove the
block device and create a sdio device and we end up calling
device_remove function twice. This changeset creates a dummy device and
then creates child based on the result of the probe. There are other
use after frees that are also fixed with this changeset.

Test:
Vim2: With ASAN: Booted with ASAN. Without this change, sdmmc crashes
in sdmmc_worker_thread. With this change, no sdmmc crash. both
SDIO/sdmmc devices show up.
Without ASAN :
- fx serve
- iochk on sdmmc device.
- wlan scan/connect/ping.
- run wlan-smoke-test GoogleGuest.
Astro: Without ASAN:Verified wlan scan/connect.
With ASAN: No sdmmc crash in sdmmc_worker_thread like on TOT. Now that's
resolved and we proceed further loading brcmfmac driver. However there
is another crash in aml_sdmmc_irq_thread. I will raise a separate bug and
submit another changeset for it.
Pixelbook:
- fx serve.
- iochk on sdmmc device.

Testing on pixelbook is in progress.

ZX-2951 #Done.

Change-Id: I9694b82138d9ba98ee66ca2da429a048479771db

Other drivers can use this code for unit tests.

Test: current (ram-nand-test)
Change-Id: I2c2480ba236806f5f3ad7d300565996ee786288c