Searched refs:device_irq_level (Results 1 – 6 of 6) sorted by relevance
373 regs->device_irq_level &= ~(KVM_ARM_DEV_EL1_VTIMER | in kvm_timer_update_run()376 regs->device_irq_level |= KVM_ARM_DEV_EL1_VTIMER; in kvm_timer_update_run()378 regs->device_irq_level |= KVM_ARM_DEV_EL1_PTIMER; in kvm_timer_update_run()640 vlevel = sregs->device_irq_level & KVM_ARM_DEV_EL1_VTIMER; in kvm_timer_should_notify_user()641 plevel = sregs->device_irq_level & KVM_ARM_DEV_EL1_PTIMER; in kvm_timer_should_notify_user()
407 bool run_level = sregs->device_irq_level & KVM_ARM_DEV_PMU; in kvm_pmu_should_notify_user()423 regs->device_irq_level &= ~KVM_ARM_DEV_PMU; in kvm_pmu_update_run()425 regs->device_irq_level |= KVM_ARM_DEV_PMU; in kvm_pmu_update_run()
123 __u64 device_irq_level; member
156 __u64 device_irq_level; member
6151 updates the vcpu's run->s.regs.device_irq_level field to represent the actual6159 of run->s.regs.device_irq_level on every kvm exit.6160 The value in run->s.regs.device_irq_level can represent both level and edge6162 signals will exit to userspace with the bit in run->s.regs.device_irq_level6165 The field run->s.regs.device_irq_level is available independent of6170 and thereby which bits in run->s.regs.device_irq_level can signal values.6172 Currently the following bits are defined for the device_irq_level bitmap::
