Am 28.11.2014 um 18:16 schrieb Paolo Bonzini:
On 28/11/2014 14:25, Christian Borntraeger wrote:
+static int __inject_prog_irq(struct kvm_vcpu *vcpu,
+ struct kvm_s390_interrupt_info *inti)
+{
Why the __s? :)
In this case because its called with a lock already
Excerpts from Paolo Bonzini's message of 2014-11-28 18:16:03 +0100:
On 28/11/2014 14:25, Christian Borntraeger wrote:
+static int __inject_prog_irq(struct kvm_vcpu *vcpu,
+ struct kvm_s390_interrupt_info *inti)
+{
Why the __s? :)
I used the __s here to say careful,
From: Jens Freimann jf...@linux.vnet.ibm.com
In preparation for the rework of the local interrupt injection code,
factor out injection routines from kvm_s390_inject_vcpu().
Signed-off-by: Jens Freimann jf...@linux.vnet.ibm.com
Reviewed-by: David Hildenbrand d...@linux.vnet.ibm.com
Signed-off-by:
On 28/11/2014 14:25, Christian Borntraeger wrote:
+static int __inject_prog_irq(struct kvm_vcpu *vcpu,
+ struct kvm_s390_interrupt_info *inti)
+{
Why the __s? :)
Paolo
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
