| /system/fidl/fuchsia-process/ |
| A D | resolver.fidl | 16 // If present, the |executable| is suitable for use as the |executable| 17 // property of |LaunchInfo|. If present, the |ldsvc| is suitable for use as 21 // and return the executable binary from the package as well as a shared
|
| /system/fidl/fuchsia-hardware-nand/ |
| A D | ram-nand.fidl | 44 // VMO to use as backing store for nand device. Size should match size of |nand_info|. 52 // Partition map for the device. This can be left fully empty (as in default-initialized), 53 // as long as no metadata has to be exported by the device. If any metadata is required, 57 bool export_nand_config; // If true, export "extra" partition configuration as metadata. 58 bool export_partition_map; // if true, export a boot partition map as metadata.
|
| /system/utest/perftest/ |
| A D | README.md | 10 For examples of how to use the testing framework, as well as coding guidelines,
|
| /system/ulib/zx/ |
| A D | README.md | 13 This library is usable both within the Zircon repo as well as the
|
| /system/fidl/zircon-usb-test-fwloader/ |
| A D | usb-test-fwloader.fidl | 21 /// Loads the prebuilt firmware onto the USB test device, and renumerates as the new device. 24 /// Loads the firmware onto the USB test device, and renumerates as the new device.
|
| /system/utest/posixio/ |
| A D | README.md | 4 loosely defined as the set of functions that fdio implements. The goal 10 returned, as the order of detection is undefined." The tests in this
|
| /system/dev/audio/lib/simple-audio-stream/ |
| A D | README.md | 9 protocol messages as well as enforcing some of the protocol state requirements.
|
| /system/ulib/fit/ |
| A D | README.md | 9 event-driven programs as the C++ 14 standard library has some limitations in 15 become a framework for writing applications. FIT can be thought of as an 23 Several Fuchsia SDK libraries, such as *libfidl*, depend on FIT and on the C++ 59 - Classes that impose an implementation burden on clients such as event loops, 77 as `std::function` except where necessary to diverge due to its move-only 102 as `std::unique_ptr`, which are helpful in these situations. Unfortunately the 114 system and it's also a building block for other features such as 128 surprised when assigning a null closure to wrappers such as fit::function 148 such as by expressing asynchronous logic as a compositions of futures.
|
| /system/ulib/zircon-internal/include/lib/zircon-internal/device/cpu-trace/ |
| A D | skylake-misc-events.inc | 38 "Memory Bytes Read", "64 byte lines read, from controller, recorded as bytes") 42 "Memory Bytes Written", "64 byte lines written, from controller, recorded as bytes") 64 "Sum of all active core cycles (in C0 state), rate is same as TSC") 69 "Sum of any active core cycles (in C0 state), rate is same as TSC") 74 "Sum of active GT cycles (in C0 state), rate is same as TSC") 79 "Sum of cycles when GT and IA are both active (in C0 state), rate is same as TSC")
|
| A D | intel-pm-events.inc | 10 // specifying the counter as either fixed or programmable. 18 // - event number as known to hardware
|
| /system/banjo/ddk-protocol-serialimpl/ |
| A D | serial-impl.banjo | 17 /// and return as soon as possible. In particular, it may not be safe to make protocol calls
|
| /system/host/fidl/include/fidl/ |
| A D | token_definitions.inc | 5 // No header inclusion guards _sic_ as this may be re-included with 48 KEYWORD(As, "as")
|
| /system/ulib/async-loop/ |
| A D | README.md | 11 - `libasync-loop.a` provides the loop implementation itself as declared in 61 ## Setting as the default async dispatcher 65 will automatically register itself as the default dispatcher for the thread on
|
| /system/ulib/trace-engine/ |
| A D | README.md | 7 to support other tracing libraries, such as libtrace, which offer higher
|
| /system/ulib/trace-vthread/ |
| A D | README.md | 6 as the latter is only intended to handle the common case; extending it to
|
| /system/host/banjo/include/banjo/ |
| A D | token_definitions.inc | 5 // No header inclusion guards _sic_ as this may be re-included with 48 KEYWORD(As, "as")
|
| /system/dev/misc/cpu-trace/ |
| A D | intel-pt.md | 17 running on the cpu, except as can be controlled by PT configuration MSRs 22 In this mode of operation individual threads are traced, even as they 105 treating the set of buffers as one large virtual buffer. 120 IPT buffers can be spread out over multiple VMOs as specified when the 174 8) *ioctl_ipt_free_trace()* [this will free each buffer as well]
|
| /system/uapp/trace-benchmark/ |
| A D | README.md | 5 to tracing, such as the overhead of instrumentation when tracing is disabled.
|
| /system/fidl/fuchsia-hardware-tee/ |
| A D | tee.fidl | 12 // Applications. This structure matches the UUID type as defined by RFC4122. 35 // A parameter will be tagged as either an input, output or both (inout). 42 // None is an empty parameter type that is used as a placeholder for elements in the parameter set
|
| /system/fidl/fuchsia-device-manager/ |
| A D | coordinator.fidl | 11 // This definition must be the same size as zx_device_prop_t and is checked by 88 /// as its primary protocol id. |args| should only be used for shadowed devices, 96 /// Behaves as AddDevice, but marks the device as initially invisible. This means 108 /// Mark this device as visible. 147 /// interfaces, but also as a backdoor for plumbing that has not been fully
|
| A D | dmctl.fidl | 14 /// interfaces, but also as a backdoor for plumbing that has not been fully
|
| /system/fidl/fuchsia-hardware-ethernet/ |
| A D | ethernet.fidl | 76 // as well as the packets we're receiving. 110 // readable from the rx fifo. The offset field will be the same as was 136 // FIFO_* flags as above
|
| /system/banjo/ddk-protocol-usb-composite/ |
| A D | usb-composite.banjo | 16 /// Marks the interface as claimed and appends the interface descriptor to the
|
| /system/banjo/ddk-protocol-badblock/ |
| A D | bad-block.banjo | 18 /// Sets |block| as bad. If block is already marked bad, it has no effect.
|
| /system/fidl/fuchsia-sysmem/ |
| A D | allocator.fidl | 43 // In the first phase, one client acts as a coordinator. The coordinator 44 // creates an event pair and designates one endpoint as the *token* and 45 // the other endpoint as the *token peer*. The coordinator then calls
|