Lines Matching refs:SError

889 such a way that a real device would generate a physical SError, KVM may make
890 a virtual SError pending for that VCPU. This system error interrupt remains
893 Running the VCPU may cause it to take a pending SError, or make an access that
894 causes an SError to become pending. The event's description is only valid while
900 guest-visible registers. It is not possible to 'cancel' an SError that has been
903 A device being emulated in user-space may also wish to generate an SError. To do
905 should be read first, to ensure no existing SError is pending. If an existing
906 SError is pending, the architecture's 'Multiple SError interrupts' rules should
910 SError exceptions always have an ESR value. Some CPUs have the ability to
911 specify what the virtual SError's ESR value should be. These systems will
913 always have a non-zero value when read, and the agent making an SError pending
966 Set the pending SError exception state for this VCPU. It is not possible to
4768 takes a virtual SError interrupt exception.
4771 CPU when the exception is taken. If this virtual SError is taken to EL1 using