| /xen/xen/drivers/acpi/apei/ |
| A D | erst.c | 282 .run = apei_exec_read_register,
298 .run = apei_exec_noop,
302 .run = erst_exec_load_var1,
306 .run = erst_exec_load_var2,
310 .run = erst_exec_store_var1,
314 .run = erst_exec_add,
318 .run = erst_exec_subtract,
322 .run = erst_exec_add_value,
330 .run = erst_exec_stall,
342 .run = erst_exec_goto,
[all …]
|
| A D | apei-base.c | 162 apei_exec_ins_func_t run; in __apei_exec_run() local
180 !ctx->ins_table[entry->instruction].run) { in __apei_exec_run()
186 run = ctx->ins_table[entry->instruction].run; in __apei_exec_run()
187 rc = run(ctx, entry); in __apei_exec_run()
220 if (ins >= ctx->instructions || !ins_table[ins].run) { in apei_exec_for_each_entry()
|
| A D | apei-internal.h | 18 apei_exec_ins_func_t run; member
|
| /xen/tools/fuzz/ |
| A D | README.oss-fuzz | 3 This directory provides fuzzing targets to be run inside Google
21 inherit the correct compiler settings and be run in a pre-setup
25 executables, which will run in oss-fuzz infrastructure.
35 To actually test the new code, you would need to run the target in
38 It is highly recommended that you run the new target for a while to
|
| A D | README.afl | 18 2. run the following commands to build:
40 4. run the fuzzer with AFL:
62 matter where you run the binary from.
|
| /xen/automation/build/ |
| A D | README.md | 15 To see the list of available containers run `make` in this
23 run the following:
72 that run old glibc (for example, CentOS 6 or SLES11SP4), you may need to add
86 able to run `make DISTRO/VERSION` to have Docker build the container
91 To login you must run `docker login registry.gitlab.com`. For more
|
| /xen/tools/tests/vpci/ |
| A D | Makefile | 9 .PHONY: run
10 run: $(TARGET) target
|
| /xen/tools/libxl/ |
| A D | check-xl-vcpupin-parse | 19 Tests various vcpu-pinning strings. If run without arguments acts
96 run () function
134 run $OPTARG
294 run $outfile
|
| /xen/tools/tests/cpu-policy/ |
| A D | Makefile | 20 .PHONY: run
21 run: $(TARGET-y) target
|
| /xen/tools/tests/vhpet/ |
| A D | Makefile | 10 .PHONY: run
11 run: $(TARGET) target
|
| /xen/docs/misc/ |
| A D | xenmon.txt | 18 o The number of times that a domain was scheduled to run (ie, dispatched) over
31 This is how much time the domain spent waiting to run, or put another way, the
32 amount of time the domain spent in the "runnable" state (or on the run queue)
76 - To see the various options for xenmon, run xenmon -h. Ditto for xenbaked.
87 - The first time xenmon is run, it attempts to allocate xen trace buffers
89 trace buffer size, run the 'setsize' program (located in tools/xentrace)
|
| /xen/tools/tests/utests/ |
| A D | run_all_tests.py | 22 testresult = unittest.TextTestRunner(verbosity=3).run(suite)
|
| /xen/ |
| A D | CHANGELOG.md | 17 - Hypervisor framework to ease porting Xen to run on hypervisors.
18 - Initial support to run on Hyper-V.
|
| /xen/tools/hotplug/Linux/systemd/ |
| A D | xen-watchdog.service.in | 2 Description=Xen-watchdog - run xen watchdog daemon
|
| /xen/docs/features/ |
| A D | qemu-deprivilege.pandoc | 19 By default, the QEMU device model is run in domain 0. If an attacker
40 For maximum security, libxl needs to run the devicemodel for each
43 aside for it. Setting up a group for all devicemodels to run at is
64 Another, less-secure way is to run all QEMUs as the same UID. To do
|
| A D | sched_credit2.pandoc | 68 run some basic workload (e.g., login into them and run simple commands),
89 contradictory and non-conclusive results so far. Need to run more of
|
| A D | sched_rtds.pandoc | 80 that they boot and can run some basic workload (e.g., login into them
81 and run simple commands),
93 * run a CPU-burning process inside the VM (e.g., `yes`),
|
| /xen/tools/hotplug/Linux/ |
| A D | locking.sh | 22 LOCK_BASEDIR=/var/run/xen-hotplug
|
| /xen/tools/debugger/gdbsx/ |
| A D | README | 7 of 32 or 64bit PV or HVM elf guest binaries. It can also be run standalone,
50 - For now, it is not possible to run gdbsx on a guest and gdb inside
52 - To report problems, please run gdbsx with -d and collect output.
|
| /xen/docs/misc/arm/ |
| A D | big.LITTLE.txt | 4 cheaper to run. For example, Cortex A53 and Cortex A57 cpus. Typically,
34 following options run all domain vcpus on either big or LITTLE cores
|
| /xen/docs/ |
| A D | README.colo | 3 (SVM) run in parallel. They receive the same request from client, and generate
|
| /xen/tools/tests/mce-test/ |
| A D | README | 62 2. run system at xen and start xend. A installed guest image is
66 4. run test cases that you want.
|
| /xen/automation/build/suse/ |
| A D | sles11sp4.dockerfile | 15 # distros nowadays disable vsyscall. To run this container, the host needs to
|
| /xen/xen/arch/x86/ |
| A D | Kconfig | 50 to run as a PV guest, but don't require any specific hardware support.
52 This option is needed if you want to run PV domains.
100 This option is needed if you want to run HVM or PVH domains.
225 Build Xen with a mode which acts as a shim to allow PV guest to run
|
| /xen/automation/scripts/ |
| A D | containerize | 95 exec ${docker_cmd} run \
|