| /openbmc/sdbusplus/include/sdbusplus/async/ |
| H A D | timer.hpp | 31 template <execution::receiver R>
44 execution::set_value(std::move(self->receiver)); in handler()
49 friend auto tag_invoke(execution::start_t, sleep_operation& self) noexcept in tag_invoke()
58 execution::set_error(std::move(self.receiver), in tag_invoke()
88 friend auto tag_invoke(execution::get_completion_signatures_t,
90 -> execution::completion_signatures<
91 execution::set_value_t(),
92 execution::set_error_t(std::exception_ptr),
93 execution::set_stopped_t()>;
95 template <execution::receiver R>
[all …]
|
| H A D | callback.hpp | 60 template <takes_msg_handler Init, execution::receiver R>
92 execution::set_value(std::move(self.receiver), std::move(msg)); in handler()
96 execution::set_error(std::move(self.receiver), in handler()
103 friend void tag_invoke(execution::start_t, in tag_invoke()
116 execution::set_error(std::move(self.receiver), in tag_invoke()
140 friend auto tag_invoke(execution::get_completion_signatures_t,
142 -> execution::completion_signatures<execution::set_value_t(message_t),
143 execution::set_stopped_t()>;
145 template <execution::receiver R>
146 friend auto tag_invoke(execution::connect_t, callback_sender&& self, R r) in tag_invoke()
|
| H A D | match.hpp | 89 friend void tag_invoke(execution::start_t, match_completion& self) noexcept in tag_invoke()
103 template <execution::receiver Receiver>
113 execution::set_value(std::move(receiver), std::move(msg)); in complete()
118 execution::set_stopped(std::move(receiver)); in stop()
132 friend auto tag_invoke(execution::get_completion_signatures_t,
134 -> execution::completion_signatures<execution::set_value_t(message_t),
135 execution::set_stopped_t()>;
137 template <execution::receiver R>
138 friend auto tag_invoke(execution::connect_t, match_sender&& self, R r) in tag_invoke()
159 execution::then([](message_t&& m) { return m.unpack<Rs...>(); }); in next()
|
| H A D | fdio.hpp | 65 friend void tag_invoke(execution::start_t, fdio_completion& self) noexcept in tag_invoke()
79 template <execution::receiver Receiver>
89 execution::set_value(std::move(receiver)); in complete()
94 execution::set_stopped(std::move(receiver)); in stop()
109 friend auto tag_invoke(execution::get_completion_signatures_t,
111 -> execution::completion_signatures<execution::set_value_t(),
112 execution::set_stopped_t()>;
114 template <execution::receiver R>
115 friend auto tag_invoke(execution::connect_t, fdio_sender&& self, R r) in tag_invoke()
|
| H A D | context.hpp | 59 template <execution::sender_of<execution::set_value_t()> Snd>
65 execution::starts_on(loop.get_scheduler(), std::move(sender)))); in spawn()
104 execution::run_loop loop{};
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/asio/asio/ |
| H A D | 0001-tests-Remove-blocking_adaptation.cpp.patch | 7 ../../../asio-1.30.2/src/tests/../../include/asio/execution/blocking_adaptation.hpp:216:13: error: …
10 …/../include/asio/execution/blocking_adaptation.hpp:213:29: note: in instantiation of exception spe…
29 unit/execution/any_executor \
30 unit/execution/blocking \
31 - unit/execution/blocking_adaptation \
32 unit/execution/context_as \
33 unit/execution/executor \
34 unit/execution/invocable_archetype \
|
| /openbmc/sdbusplus/src/async/ |
| H A D | context.cpp | 50 template <execution::receiver R>
61 execution::set_value(std::move(this->receiver)); in complete()
68 execution::set_value(std::move(this->receiver)); in stop()
71 friend void tag_invoke(execution::start_t, in tag_invoke()
87 friend auto tag_invoke(execution::get_completion_signatures_t,
89 -> execution::completion_signatures<execution::set_value_t()>;
91 template <execution::receiver R>
92 friend auto tag_invoke(execution::connect_t, wait_process_sender&& self, in tag_invoke()
106 co_await execution::continues_on(wait_process_sender(ctx), in loop()
197 execution::then([this]() { spawn_complete(); })); in spawn_watcher()
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 85 …27] exdebug-0398 ex_trace_point : Method Begin [0xf58394d8:\_SB.PCI0.LPCB.ECOK] execution.
86 [ 0.186630] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905c88:If] execution.
87 [ 0.186820] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905cc0:LEqual] execution.
88 … 0.187010] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905a20:-NamePath-] execution.
89 …[ 0.187214] exdebug-0398 ex_trace_point : Opcode End [0xf5905a20:-NamePath-] execution.
90 [ 0.187407] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution.
91 [ 0.187594] exdebug-0398 ex_trace_point : Opcode End [0xf5905f60:One] execution.
92 [ 0.187789] exdebug-0398 ex_trace_point : Opcode End [0xf5905cc0:LEqual] execution.
93 [ 0.187980] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905cc0:Return] execution.
94 [ 0.188146] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution.
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | replay.json | 16 # @none: normal execution mode. Replay or record are not enabled.
22 # execution is read from the log.
105 # replaying the execution. The command automatically loads nearest
106 # snapshot and replays the execution to find the desired instruction.
107 # When there is no preceding snapshot or the execution is not
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | bpf_prog_run.rst | 49 returned to userspace. A separate mode for live execution of XDP programs is
57 be processed by the kernel after the execution of the XDP program as if they
62 The live packet mode is optimised for high performance execution of the supplied
67 - When executing an XDP program in live frame mode, the result of the execution
73 specifically, only fatal errors in setup or during execution (like memory
74 allocation errors) will halt execution and return an error. If an error occurs
76 execution will continue with the next repetition; these errors can be detected
86 because the program execution is not happening in driver context, an
91 - When running the program with multiple repetitions, the execution will happen
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | legacy_instructions.rst | 9 the instruction execution in hardware.
12 (/proc/sys/abi). The following explains the different execution
33 enabling/disabling of hardware support for the execution of these
34 instructions. Using hardware execution generally provides better
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | workqueue.rst | 13 There are many cases where an asynchronous process execution context
17 When such an asynchronous execution context is needed, a work item
19 independent thread serves as the asynchronous execution context. The
42 worker pool. An MT wq could provide only one execution context per CPU
44 those very limited execution contexts leading to various problems
45 including proneness to deadlocks around the single execution context.
71 In order to ease the asynchronous execution of functions a new
110 (how many execution contexts are active) is an important issue. cmwq
122 workers on the CPU, the worker-pool doesn't start execution of a new
126 without losing execution bandwidth.
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | replay.rst | 13 Record/replay functions are used for the deterministic replay of qemu execution.
15 used for replaying the execution anywhere and for unlimited number of times.
22 * Deterministically replays whole system execution and all contents of
24 * Writes execution log into the file for later replaying for multiple times
34 * First, record the execution with the following command line:
81 simulated hardware, memory of VM, software interrupts, and execution of
90 designed to allow deterministic execution in absence of external inputs
92 command-line option, making possible deterministic execution of the machine,
131 the execution.
211 Reverse step loads the nearest snapshot and replays the execution until
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | replay.rst | 13 execution. Execution recording writes a non-deterministic events log, which
14 can be later used for replaying the execution anywhere and for unlimited
22 changed to write every external event into the execution log immediately.
40 * synchronization of the bottom halves execution
53 designed to allow deterministic execution in absence of external inputs
56 is written to the log while recording the execution. In replay mode we
70 written but now it is held for a whole execution period. This results
84 Replaying the execution of virtual machine is bound by sources of
101 execution and timer events.
124 the guest state during execution in icount mode should be deterministic.
[all …]
|
| H A D | tcg-icount.rst | 11 instruction counting during execution. This should not be confused
19 execution time with wall-clock time so a "slow" device doesn't run too
21 deterministic execution and is an essential part of the record/replay
31 execution started. Depending on the icount mode this may either be a
32 fixed number of ns per instruction or adjusted as execution continues
|
| /openbmc/qemu/docs/interop/ |
| H A D | qmp-spec.rst | 90 execution, as described in section `Out-of-band execution`_.
95 The format for command execution is:
110 executed by the server. The latter requests out-of-band execution.
112 execution of the command, it is optional when no arguments are
116 command execution, it is optional and will be part of the response
122 Out-of-band execution
129 With out-of-band execution enabled via `capabilities negotiation`_,
148 Only a few commands support out-of-band execution. The ones that do
155 of a command execution: success or error.
179 with the command execution if issued by the Client.
[all …]
|
| /openbmc/u-boot/arch/arm/mach-sunxi/ |
| H A D | rmr_switch.S | 9 @ into a different execution state (AArch32 or AArch64).
10 @ The address at which execution starts after the reset is held in the
14 @ This code below switches to AArch64 and starts execution at the specified
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 7 and speculative execution on modern CPUs to read memory, possibly
8 bypassing access controls. Speculative execution side channel exploits
16 Speculative execution side channel methods affect a wide range of modern
18 use branch prediction and speculative execution.
56 influence the speculative execution paths, and then use the side effects
57 of the speculative execution in the CPUs' caches and buffers to infer
58 privileged data touched during the speculative execution.
60 Spectre variant 1 attacks take advantage of speculative execution of
62 execution of indirect branches to leak privileged memory.
70 of speculative execution that bypasses conditional branch instructions
[all …]
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | scons.bbclass | 28 die "scons build execution failed."
33 die "scons install execution failed."
|
| /openbmc/sdbusplus/example/ |
| H A D | calculator-client.cpp | 77 sdbusplus::async::execution::just() | in main()
78 sdbusplus::async::execution::then([&ctx]() { ctx.request_stop(); })); in main()
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | test_bmc_reset_loop.robot | 32 # Fails immediately if any of the execution rounds fail and
42 # Fails immediately if any of the execution rounds fail and
52 # Fails immediately if any of the execution rounds fail and
62 # Fails immediately if any of the execution rounds fail and
|
| /openbmc/sdbusplus/test/async/ |
| H A D | fdio.cpp | 87 sdbusplus::async::execution::then([&]() { ctx->request_stop(); })); in TEST_F()
98 sdbusplus::async::execution::then([&]() { ctx->request_stop(); })); in TEST_F()
|
| /openbmc/linux/Documentation/trace/ |
| H A D | osnoise-tracer.rst | 25 the latency. The hwlat detects the NMI execution by observing
30 all the sources of *osnoise* during its execution. Using the same approach
151 the thread_noise, starting a irq_noise. When the IRQ ends its execution,
154 IRQ execution. This logic is valid for all sources of noise.
166 timer IRQ execution. The first event is not part of the noise because
172 before and after any interference execution. This justifies the dual
179 the osnoise: tracepoints serve to measure the execution time of
|
| /openbmc/u-boot/doc/ |
| H A D | README.mpc85xx | 40 TLB Entries during u-boot execution
43 Note: Sequence number is in order of execution
65 4) TLB entry for CCSRBAR during AS1 execution
121 4) TLB entry for CCSRBAR during AS1 execution
|
| /openbmc/qemu/docs/about/ |
| H A D | emulation.rst | 122 ``SYS_READC``) can block execution indefinitely. You should only
185 translation and execution and optionally callback into the plugin
249 A very basic plugin which will measure execution in coarse terms as
251 execution finishes::
269 - Dump the current execution stats whenever the guest vCPU idles
334 - Give a summary of the instruction sizes for the execution
339 instructions have executed since the last execution. For
354 For more detailed execution tracing see the ``execlog`` plugin for
445 execution are in your program. Once the program has finished you will
447 count, number of instructions and execution count. This will work best
[all …]
|