mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-07 09:43:56 -06:00
5e691a955a
There are (at least) three different vCPU ID number spaces. One is the internal KVM vCPU index, based purely on which vCPU was chronologically created in the kernel first. If userspace threads are all spawned and create their KVM vCPUs in essentially random order, then the KVM indices are basically random too. The second number space is the APIC ID space, which is consistent and useful for referencing vCPUs. MSIs will specify the target vCPU using the APIC ID, for example, and the KVM Xen APIs also take an APIC ID from userspace whenever a vCPU needs to be specified (as opposed to just using the appropriate vCPU fd). The third number space is not normally relevant to the kernel, and is the ACPI/MADT/Xen CPU number which corresponds to cs->cpu_index. But Xen timer hypercalls use it, and Xen timer hypercalls *really* want to be accelerated in the kernel rather than handled in userspace, so the kernel needs to be told. Signed-off-by: David Woodhouse <dwmw@amazon.co.uk> Reviewed-by: Paul Durrant <paul@xen.org> |
||
|---|---|---|
| .. | ||
| hax | ||
| hvf | ||
| kvm | ||
| nvmm | ||
| tcg | ||
| whpx | ||
| arch_dump.c | ||
| arch_memory_mapping.c | ||
| cpu-dump.c | ||
| cpu-internal.h | ||
| cpu-param.h | ||
| cpu-qom.h | ||
| cpu-sysemu.c | ||
| cpu.c | ||
| cpu.h | ||
| gdbstub.c | ||
| helper.c | ||
| helper.h | ||
| host-cpu.c | ||
| host-cpu.h | ||
| Kconfig | ||
| machine.c | ||
| meson.build | ||
| monitor.c | ||
| ops_sse.h | ||
| ops_sse_header.h | ||
| sev-sysemu-stub.c | ||
| sev.c | ||
| sev.h | ||
| shift_helper_template.h | ||
| svm.h | ||
| trace-events | ||
| trace.h | ||
| xsave_helper.c | ||