Lines Matching refs:SError

1079 such a way that a real device would generate a physical SError, KVM may make
1080 a virtual SError pending for that VCPU. This system error interrupt remains
1083 Running the VCPU may cause it to take a pending SError, or make an access that
1084 causes an SError to become pending. The event's description is only valid while
1090 guest-visible registers. It is not possible to 'cancel' an SError that has been
1093 A device being emulated in user-space may also wish to generate an SError. To do
1095 should be read first, to ensure no existing SError is pending. If an existing
1096 SError is pending, the architecture's 'Multiple SError interrupts' rules should
1100 SError exceptions always have an ESR value. Some CPUs have the ability to
1101 specify what the virtual SError's ESR value should be. These systems will
1103 always have a non-zero value when read, and the agent making an SError pending
1175 Set the pending SError exception state for this VCPU. It is not possible to
6288 takes a virtual SError interrupt exception.
6291 CPU when the exception is taken. If this virtual SError is taken to EL1 using