Searched refs:device_irq_level (Results 1 – 7 of 7) sorted by relevance
265 regs->device_irq_level &= ~(KVM_ARM_DEV_EL1_VTIMER | in kvm_timer_update_run()268 regs->device_irq_level |= KVM_ARM_DEV_EL1_VTIMER; in kvm_timer_update_run()270 regs->device_irq_level |= KVM_ARM_DEV_EL1_PTIMER; in kvm_timer_update_run()522 vlevel = sregs->device_irq_level & KVM_ARM_DEV_EL1_VTIMER; in kvm_timer_should_notify_user()523 plevel = sregs->device_irq_level & KVM_ARM_DEV_EL1_PTIMER; in kvm_timer_should_notify_user()
231 bool run_level = sregs->device_irq_level & KVM_ARM_DEV_PMU; in kvm_pmu_should_notify_user()247 regs->device_irq_level &= ~KVM_ARM_DEV_PMU; in kvm_pmu_update_run()249 regs->device_irq_level |= KVM_ARM_DEV_PMU; in kvm_pmu_update_run()
152 __u64 device_irq_level; member
123 __u64 device_irq_level; member
4654 updates the vcpu's run->s.regs.device_irq_level field to represent the actual4662 of run->s.regs.device_irq_level on every kvm exit.4663 The value in run->s.regs.device_irq_level can represent both level and edge4665 signals will exit to userspace with the bit in run->s.regs.device_irq_level4668 The field run->s.regs.device_irq_level is available independent of4673 and thereby which bits in in run->s.regs.device_irq_level can signal values.4675 Currently the following bits are defined for the device_irq_level bitmap:
