Searched refs:synic (Results 1 – 8 of 8) sorted by relevance
216 return (synic->active) ? synic : NULL; in synic_get()252 hv_vcpu->exit.u.synic.control = synic->control; in synic_exit()253 hv_vcpu->exit.u.synic.evt_page = synic->evt_page; in synic_exit()254 hv_vcpu->exit.u.synic.msg_page = synic->msg_page; in synic_exit()273 synic->control = data; in synic_set_msr()282 synic->version = data; in synic_set_msr()311 if (!synic->active) in synic_set_msr()505 if (!synic) in kvm_hv_synic_set_irq()528 if (!synic) in kvm_hv_set_sint_gsi()560 memset(synic, 0, sizeof(*synic)); in synic_init()[all …]
73 return &hv_vcpu->synic; in to_hv_synic()76 static inline struct kvm_vcpu *hv_synic_to_vcpu(struct kvm_vcpu_hv_synic *synic) in hv_synic_to_vcpu() argument78 struct kvm_vcpu_hv *hv_vcpu = container_of(synic, struct kvm_vcpu_hv, synic); in hv_synic_to_vcpu()
168 Synthetic Interrupt Controller (synic)171 that is used by VMBus for host-guest communication. While each synic178 each CPU in the guest has a synic and may receive VMBus interrupts,188 The synic provides the means to demultiplex the architectural interrupt into191 related functions that access synic data structures.193 The synic is not modeled in Linux as an irq chip or irq domain,210 Similarly, the host will interrupt the guest via the synic when216 for channel interrupts by calling vmbus_chan_sched(), which looks at a synic
181 * Synthetic interrupt controller (synic) related pages (unless supplied by
106 } synic; member
677 struct kvm_vcpu_hv_synic synic; member
6942 } synic;