Searched refs:device_irq_level (Results 1 – 10 of 10) sorted by relevance
1262 if (run->s.regs.device_irq_level != cpu->device_irq_level) { in kvm_arch_post_run()1263 switched_level = cpu->device_irq_level ^ run->s.regs.device_irq_level; in kvm_arch_post_run()1269 !!(run->s.regs.device_irq_level & in kvm_arch_post_run()1276 !!(run->s.regs.device_irq_level & in kvm_arch_post_run()1283 !!(run->s.regs.device_irq_level & KVM_ARM_DEV_PMU)); in kvm_arch_post_run()1293 cpu->device_irq_level = run->s.regs.device_irq_level; in kvm_arch_post_run()
1093 uint8_t device_irq_level; member
437 regs->device_irq_level &= ~(KVM_ARM_DEV_EL1_VTIMER | in kvm_timer_update_run()440 regs->device_irq_level |= KVM_ARM_DEV_EL1_VTIMER; in kvm_timer_update_run()442 regs->device_irq_level |= KVM_ARM_DEV_EL1_PTIMER; in kvm_timer_update_run()868 vlevel = sregs->device_irq_level & KVM_ARM_DEV_EL1_VTIMER; in kvm_timer_should_notify_user()869 plevel = sregs->device_irq_level & KVM_ARM_DEV_EL1_PTIMER; in kvm_timer_should_notify_user()
360 bool run_level = sregs->device_irq_level & KVM_ARM_DEV_PMU; in kvm_pmu_should_notify_user()376 regs->device_irq_level &= ~KVM_ARM_DEV_PMU; in kvm_pmu_update_run()378 regs->device_irq_level |= KVM_ARM_DEV_PMU; in kvm_pmu_update_run()
123 __u64 device_irq_level; member
162 __u64 device_irq_level; member
160 __u64 device_irq_level; member
7873 updates the vcpu's run->s.regs.device_irq_level field to represent the actual7881 of run->s.regs.device_irq_level on every kvm exit.7882 The value in run->s.regs.device_irq_level can represent both level and edge7884 signals will exit to userspace with the bit in run->s.regs.device_irq_level7887 The field run->s.regs.device_irq_level is available independent of7892 and thereby which bits in run->s.regs.device_irq_level can signal values.7894 Currently the following bits are defined for the device_irq_level bitmap::