From: gang.chen.5i5j@gmail.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] virt: kvm: arm: vgic: Return failure code '-EBUSY' when mutex_trylock() fails
Date: Wed, 12 Nov 2014 23:04:23 +0800 [thread overview]
Message-ID: <546376F7.90502@gmail.com> (raw)
When mutex_trylock() fails, kvm_vgic_create() will not create 'vgic', so
it need return failure code '-EBUSY' instead of '0' to let outside know
about it.
Also simplify the code within kvm_vgic_create():
- kvm_for_each_vcpu() scanning once is enough for current case.
- Remove redundant variable 'vcpu_lock_idx'.
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
virt/kvm/arm/vgic.c | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
index 3aaca49..5846725 100644
--- a/virt/kvm/arm/vgic.c
+++ b/virt/kvm/arm/vgic.c
@@ -1933,7 +1933,7 @@ out:
int kvm_vgic_create(struct kvm *kvm)
{
- int i, vcpu_lock_idx = -1, ret = 0;
+ int i, ret = 0;
struct kvm_vcpu *vcpu;
mutex_lock(&kvm->lock);
@@ -1949,13 +1949,12 @@ int kvm_vgic_create(struct kvm *kvm)
* that no other VCPUs are run while we create the vgic.
*/
kvm_for_each_vcpu(i, vcpu, kvm) {
- if (!mutex_trylock(&vcpu->mutex))
+ if (!mutex_trylock(&vcpu->mutex)) {
+ ret = -EBUSY;
goto out_unlock;
- vcpu_lock_idx = i;
- }
-
- kvm_for_each_vcpu(i, vcpu, kvm) {
+ }
if (vcpu->arch.has_run_once) {
+ mutex_unlock(&vcpu->mutex);
ret = -EBUSY;
goto out_unlock;
}
@@ -1968,8 +1967,8 @@ int kvm_vgic_create(struct kvm *kvm)
kvm->arch.vgic.vgic_cpu_base = VGIC_ADDR_UNDEF;
out_unlock:
- for (; vcpu_lock_idx >= 0; vcpu_lock_idx--) {
- vcpu = kvm_get_vcpu(kvm, vcpu_lock_idx);
+ while (i-- > 0) {
+ vcpu = kvm_get_vcpu(kvm, i);
mutex_unlock(&vcpu->mutex);
}
--
1.9.3
next reply other threads:[~2014-11-12 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 15:04 Chen Gang [this message]
2014-11-12 19:41 ` [PATCH] virt: kvm: arm: vgic: Return failure code '-EBUSY' when mutex_trylock() fails Christoffer Dall
2014-11-13 2:34 ` Chen Gang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=546376F7.90502@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).