| commit | 85ca3371f6f5284d54202aec091e7cb3a49e5135 | |
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | |
| Thu, 28 Aug 2014 11:58:49 +0000 (28 13:58 +0200) | ||
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Mon, 1 Sep 2014 07:23:02 +0000 (1 09:23 +0200) | ||
| tree | a293cda663b5eebd4a92006f92a0944f73f49ccd | treesnapshot (tar.gz zip) |
| parent | 8b3030114a449e66c68450acaac4b66f26d91416 | commitdiff |
s390x/kvm: run guest triggered resets on the target vcpu thread
Currently, load_normal_reset() and modified_clear_reset() as triggered
by a guest vcpu will initiate cpu resets on the current vcpu thread for
all cpus. The reset should happen on the individual vcpu thread
instead, so let's use run_on_cpu() for this.
This avoids calls to synchronize_rcu() in the kernel.
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Currently, load_normal_reset() and modified_clear_reset() as triggered
by a guest vcpu will initiate cpu resets on the current vcpu thread for
all cpus. The reset should happen on the individual vcpu thread
instead, so let's use run_on_cpu() for this.
This avoids calls to synchronize_rcu() in the kernel.
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
| target-s390x/cpu.h | diffblobblamehistory | |
| target-s390x/misc_helper.c | diffblobblamehistory |