| /f-stack/freebsd/amd64/vmm/intel/ |
| H A D | vmcs.c | 216 if (!running) in vmcs_getreg()
221 if (!running) in vmcs_getreg()
243 if (!running) in vmcs_setreg()
248 if (!running) in vmcs_setreg()
264 if (!running) in vmcs_setdesc()
277 if (!running) in vmcs_setdesc()
293 if (!running) in vmcs_getdesc()
309 if (!running) in vmcs_getdesc()
441 if (!running) in vmcs_getany()
446 if (!running) in vmcs_getany()
[all …]
|
| H A D | vmcs.h | 55 int vmcs_getreg(struct vmcs *vmcs, int running, int ident, uint64_t *rv);
56 int vmcs_setreg(struct vmcs *vmcs, int running, int ident, uint64_t val);
57 int vmcs_getdesc(struct vmcs *vmcs, int running, int ident,
59 int vmcs_setdesc(struct vmcs *vmcs, int running, int ident,
62 int vmcs_getany(struct vmcs *vmcs, int running, int ident, uint64_t *val);
63 int vmcs_setany(struct vmcs *vmcs, int running, int ident, uint64_t val);
64 int vmcs_snapshot_reg(struct vmcs *vmcs, int running, int ident,
66 int vmcs_snapshot_desc(struct vmcs *vmcs, int running, int seg,
68 int vmcs_snapshot_any(struct vmcs *vmcs, int running, int ident,
|
| H A D | vmx.c | 1250 if (!running) { in vmx_invvpid()
3341 int running, hostcpu; in vmx_getreg() local
3345 if (running && hostcpu != curcpu) in vmx_getreg()
3366 if (running && hostcpu != curcpu) in vmx_setreg()
3427 int hostcpu, running; in vmx_getdesc() local
3431 if (running && hostcpu != curcpu) in vmx_getdesc()
3440 int hostcpu, running; in vmx_setdesc() local
3444 if (running && hostcpu != curcpu) in vmx_setdesc()
4172 int error, running, hostcpu; in vmx_restore_tsc() local
4183 if (!running) in vmx_restore_tsc()
[all …]
|
| /f-stack/app/redis-5.0.5/utils/ |
| H A D | redis_init_script.tpl | 6 echo "$PIDFILE exists, process is already running or crashed"
15 echo "$PIDFILE does not exist, process is not running"
32 echo 'Redis is not running'
34 echo "Redis is running ($PID)"
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | rte_flow.rst | 76 Terminal 2: running scapy::
90 Terminal 1: running sample the app flow rule enabled::
95 Terminal 2: running scapy::
169 Terminal 1: running sample app flow rule disabled::
174 Terminal 2: running scapy::
191 Terminal 1: running sample app flow rule enabled::
196 Terminal 2: running scapy::
263 Terminal 1: running sample app flow rule disabled::
268 Terminal 2: running scapy::
285 Terminal 1: running sample app flow rule enabled::
[all …]
|
| /f-stack/freebsd/kern/ |
| H A D | subr_autoconf.c | 121 static int running; in run_interrupt_driven_config_hooks() local
132 if (running != 0) { in run_interrupt_driven_config_hooks()
136 running = 1; in run_interrupt_driven_config_hooks()
146 running = 0; in run_interrupt_driven_config_hooks()
|
| H A D | uipc_ktls.c | 84 bool running; member
1617 bool running; in ktls_check_rx() local
1649 running = wq->running; in ktls_check_rx()
1651 if (!running) in ktls_check_rx()
1939 bool running; in ktls_enqueue_to_free() local
1946 running = wq->running; in ktls_enqueue_to_free()
1948 if (!running) in ktls_enqueue_to_free()
1956 bool running; in ktls_enqueue() local
1976 running = wq->running; in ktls_enqueue()
1978 if (!running) in ktls_enqueue()
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sound/ |
| H A D | soc-ac97link.txt | 8 "ac97-running": AC97-link is active
20 pinctrl-names = "default", "ac97-running", "ac97-reset", "ac97-warm-reset";
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | pipeline.rst | 43 * Argument: IP Address of the host running the application to be used by
52 * Argument: TCP port number at which the application is running.
55 Refer to *DPDK Getting Started Guide* for general information on running applications and the Envir…
81 When running a telnet client as above, command prompt is displayed:
93 Once application and telnet client start running, messages can be sent from client to application.
|
| H A D | service_cores.rst | 74 /* The application sets the service to running state. Note that this
115 Note that it is not allowed to remove a service core if the service is running,
116 and the service-core is the only core running that service (see documentation
127 method of registering functions to be run, allowing the running of the
|
| H A D | bbdev_app.rst | 64 using the allow option for pci device running on 1 encoding lcore and 1 decoding lcore
87 Refer to the *DPDK Getting Started Guide* for general information on running
114 Refer to *The Pktgen Application* documents for general information on running
|
| /f-stack/freebsd/contrib/device-tree/Bindings/timer/ |
| H A D | brcm,bcm2835-system-timer.txt | 4 single 64-bit free running counter. Each channel has an output compare
6 free running counter values, and generates an interrupt.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/ |
| H A D | intel,stratix10-svc.txt | 11 Layer 3) can interface with SDM. All software entities running on other
15 Intel Stratix10 service layer driver, running at privileged exception level
19 code running in EL3.
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | intro.rst | 10 For programming examples and for instructions on compiling and running each sample application,
13 For general information on compiling and running applications, see the *DPDK Getting Started Guide*.
25 designed to get users up and running quickly with the software.
|
| H A D | service_cores.rst | 14 running services). The power of the service core concept is that the mapping
41 lcore in question from running the service.
54 profile the services running on the system at any time.
|
| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | intro.rst | 8 It is designed to get customers up and running quickly.
20 …ibes how to install and configure the DPDK; designed to get users up and running quickly with the …
|
| H A D | enable_func.rst | 75 When running as non-root user, there may be some additional resource limits
89 resources also should be accessible by the user running the DPDK application.
101 The instructions below will allow running DPDK with ``igb_uio`` or
145 To help prevent additional workloads from running on those cores,
158 …sample application, an extra kernel module (the kni module) must be loaded into the running kernel.
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/inheritance/ |
| H A D | state012.cfg | 33 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
39 # running it at the top level is somewhat redundant as the top level value
|
| H A D | state014.cfg | 33 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
39 # running it at the top level is somewhat redundant as the top level value
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/channel_program/lua_core/ |
| H A D | tst.lib_coroutine.lua | 28 local main, ismain = coroutine.running()
45 local x, y = coroutine.running()
225 assert(coroutine.running() == current_co)
281 assert(coroutine.running() == main)
|
| /f-stack/freebsd/contrib/device-tree/Bindings/ |
| H A D | jailhouse.txt | 4 When running in a non-root Jailhouse cell (partition), the device tree of this
|
| /f-stack/freebsd/contrib/device-tree/Bindings/watchdog/ |
| H A D | brcm,bcm7038-wdt.txt | 10 - clocks: The clock running the watchdog. If no clock is found the
|
| /f-stack/dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_sample_apps.rst | 52 #. The ``contigmem`` and ``nic_uio`` modules must be set up prior to running an application.
55 as described in section :ref:`binding_network_ports`, prior to running the application.
60 A large number of options can be given to the EAL when running an
|
| H A D | intro.rst | 9 up and running quickly and describes how to compile and run a
33 configure the DPDK; designed to get users up and running quickly with the
|
| /f-stack/freebsd/contrib/device-tree/Bindings/security/tpm/ |
| H A D | google,cr50.txt | 3 H1 Secure Microcontroller running Cr50 firmware provides several
|