diff options
author | Bibo Mao <maobibo@loongson.cn> | 2024-05-06 17:00:47 +0300 |
---|---|---|
committer | Huacai Chen <chenhuacai@loongson.cn> | 2024-05-06 17:00:47 +0300 |
commit | 74c16b2e2b0c3b193324f47300fd30cf03a606b7 (patch) | |
tree | d44f09842b78696110c39849488eb5a4adf2e8d9 /drivers/hid/hid-appleir.c | |
parent | e33bda7ee50c3c20d80f5ca6dc5ca2cd37863518 (diff) | |
download | linux-74c16b2e2b0c3b193324f47300fd30cf03a606b7.tar.xz |
LoongArch: KVM: Add PV IPI support on guest side
PARAVIRT config option and PV IPI is added for the guest side, function
pv_ipi_init() is used to add IPI sending and IPI receiving hooks. This
function firstly checks whether system runs in VM mode, and if kernel
runs in VM mode, it will call function kvm_para_available() to detect
the current hypervirsor type (now only KVM type detection is supported).
The paravirt functions can work only if current hypervisor type is KVM,
since there is only KVM supported on LoongArch now.
PV IPI uses virtual IPI sender and virtual IPI receiver functions. With
virtual IPI sender, IPI message is stored in memory rather than emulated
HW. IPI multicast is also supported, and 128 vcpus can received IPIs
at the same time like X86 KVM method. Hypercall method is used for IPI
sending.
With virtual IPI receiver, HW SWI0 is used rather than real IPI HW.
Since VCPU has separate HW SWI0 like HW timer, there is no trap in IPI
interrupt acknowledge. Since IPI message is stored in memory, there is
no trap in getting IPI message.
Signed-off-by: Bibo Mao <maobibo@loongson.cn>
Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
Diffstat (limited to 'drivers/hid/hid-appleir.c')
0 files changed, 0 insertions, 0 deletions