mirror of
https://github.com/opnsense/src.git
synced 2026-06-10 17:22:46 -04:00
892feec221
A vcpu only checks if a rendezvous is in progress or not to decide if it should handle a rendezvous. This could lead to spurios rendezvous where a vcpu tries a handle a rendezvous it isn't part of. This situation is properly handled by vm_handle_rendezvous but it could potentially degrade the performance. Avoid that by an early check if the vcpu is part of the rendezvous or not. At the moment, rendezvous are only used to spin up application processors and to send ioapic interrupts. Spinning up application processors is done in the guest boot phase by sending INIT SIPI sequences to single vcpus. This is known to cause spurious rendezvous and only occurs in the boot phase. Sending ioapic interrupts is rare because modern guest will use msi and the rendezvous is always send to all vcpus. Reviewed by: jhb MFC after: 1 week Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D37390 |
||
|---|---|---|
| .. | ||
| amdiommu.c | ||
| amdv.c | ||
| amdvi_hw.c | ||
| amdvi_priv.h | ||
| ivhd_if.m | ||
| ivrs_drv.c | ||
| npt.c | ||
| npt.h | ||
| svm.c | ||
| svm.h | ||
| svm_genassym.c | ||
| svm_msr.c | ||
| svm_msr.h | ||
| svm_softc.h | ||
| svm_support.S | ||
| vmcb.c | ||
| vmcb.h | ||