Home
last modified time | relevance | path

Searched refs:processes (Results 1 – 25 of 38) sorted by relevance

12

/qemu/gdbstub/
H A Dsystem.c46 g_free(gdbserver_state.processes); in reset_gdbserver_state()
47 gdbserver_state.processes = NULL; in reset_gdbserver_state()
95 s->processes[i].attached = !i; in gdb_chr_event()
288 s->processes = g_renew(GDBProcess, s->processes, ++s->process_num); in find_cpu_clusters()
290 process = &s->processes[s->process_num - 1]; in find_cpu_clusters()
326 if (gdbserver_state.processes) { in create_processes()
328 qsort(gdbserver_state.processes, in create_processes()
330 sizeof(gdbserver_state.processes[0]), in create_processes()
H A Duser.c294 gdbserver_state.processes[0].attached = true; in gdb_accept_init()
574 g_assert(gdbserver_state.processes[0].pid == in gdbserver_fork_end()
576 g_assert(gdbserver_state.processes[0].attached); in gdbserver_fork_end()
577 gdbserver_state.processes[0].pid = getpid(); in gdbserver_fork_end()
H A Dgdbstub.c210 return gdbserver_state.processes[index].pid; in gdb_get_cpu_pid()
222 return &gdbserver_state.processes[0]; in gdb_get_process()
226 if (gdbserver_state.processes[i].pid == pid) { in gdb_get_process()
227 return &gdbserver_state.processes[i]; in gdb_get_process()
2487 pid = s->processes[s->process_num - 1].pid; in gdb_create_default_process()
2496 s->processes = g_renew(GDBProcess, s->processes, ++s->process_num); in gdb_create_default_process()
2497 process = &s->processes[s->process_num - 1]; in gdb_create_default_process()
H A Dinternals.h62 GDBProcess *processes; member
/qemu/docs/interop/
H A Ddbus.rst8 QEMU may be running with various helper processes involved:
9 - vhost-user* processes (gpu, virtfs, input, etc...)
17 Having several processes allows stricter security rules, as well as
25 Using a bus, helper processes can discover and communicate with each
52 processes that are connected to it. It is thus a good idea to run
/qemu/qga/
H A Dcommands.c108 QTAILQ_HEAD(, GuestExecInfo) processes;
110 .processes = QTAILQ_HEAD_INITIALIZER(guest_exec_state.processes),
129 QTAILQ_INSERT_TAIL(&guest_exec_state.processes, gei, next); in guest_exec_info_add()
138 QTAILQ_FOREACH(gei, &guest_exec_state.processes, next) { in guest_exec_info_find()
218 QTAILQ_REMOVE(&guest_exec_state.processes, gei, next); in qmp_guest_exec_status()
/qemu/docs/tools/
H A Dqemu-trace-stap.rst81 existing running processes and all future launched processes,
93 For example, to monitor all processes executing |qemu_system|
106 To monitor QEMU processes running an alternative binary outside of
/qemu/docs/devel/
H A Dmulti-process.rst44 host processes. Each of these processes can be given only the privileges
64 Separating IO services into individual host processes is a good place to
206 Remote emulation processes
215 The processes will communicate with the QEMU process over UNIX domain
216 sockets. The processes can be executed either as standalone processes,
218 processes will provide are specified on its command line, as they would
229 Emulation processes may emulate more than one guest controller. A common
247 Remote emulation processes can be monitored via QMP, similar to QEMU argument
273 QEMU management of remote processes
911 enforce that the differing processes can only access the objects they
[all …]
H A Duefi-vars.rst24 mode via SMI. The SMM code processes the request, stores the reply in
H A Dbuild-environment.rst112 Meson detects x86_64 processes emulated, so you need to manually set the cpu,
H A Dsubmitting-a-pull-request.rst44 have passed the standard code review processes. In particular if you've
/qemu/docs/system/
H A Dsecurity.rst112 The fundamental isolation mechanism is that QEMU processes must run as
121 - SELinux and AppArmor make it possible to confine processes beyond the
123 process from accessing processes and files on the host system that are not
149 and/or trigger spawning of external processes.
152 processes for the purpose of tunnelling the migration data stream. The
H A Dsecrets.rst79 that needs access. This will prevent other processes/users from compromising the
/qemu/docs/user/
H A Dindex.rst9 processes compiled for one CPU on another CPU.
/qemu/docs/devel/migration/
H A Ddirty-limit.rst64 is ACCEPT PENALTY (4). Virtual CPUs tied with writing processes will
66 with read processes will not.
H A Dcompatibility.rst7 When we do migration, we have two QEMU processes: the source and the
70 Now it comes the interesting ones, when both QEMU processes are
471 Now the interesting ones. When the QEMU processes versions are
/qemu/docs/spin/
H A Dtcg-exclusive.promela23 #warning defaulting to 2 CPU processes
178 // Promela processes
/qemu/docs/about/
H A Dindex.rst15 where QEMU can launch processes compiled for one CPU on another CPU.
/qemu/python/
H A DPACKAGE.rst13 facilities for launching and managing QEMU processes. Refer to each
/qemu/docs/devel/testing/
H A Dblkverify.rst11 processes inside the guest will crash because corrupt sectors were read as part
/qemu/docs/specs/
H A Dppc-spapr-uv-hcalls.rst10 inaccessible to normal processes/guests running on the host.
H A Dfsi.rst15 processes and so comes with some baggage, including how it has been integrated
H A Drapl-msr.rst134 A socket communication is established between QEMU processes that has the RAPL
/qemu/accel/tcg/
H A Dldst_atomicity.c.inc160 * provides no protection across processes.
197 * provides no protection across processes.
/qemu/qapi/
H A Djob.json53 # by either the QMP user or by internal processes.

12