From: Chen Gang <gang.chen.5i5j@gmail.com>
To: "christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
"gleb@kernel.org" <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH] kvm: arm: vgic: Let one looping code instead of two looping code
Date: Sun, 30 Nov 2014 12:18:04 +0800 [thread overview]
Message-ID: <547A9A7C.1080508@gmail.com> (raw)
Use one looping instead of two, so can let code more simpler and get a
little better performance.
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
virt/kvm/arm/vgic.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
index cf23c13..eb1a51b 100644
--- a/virt/kvm/arm/vgic.c
+++ b/virt/kvm/arm/vgic.c
@@ -1959,9 +1959,6 @@ int kvm_vgic_create(struct kvm *kvm)
if (!mutex_trylock(&vcpu->mutex))
goto out_unlock;
vcpu_lock_idx = i;
- }
-
- kvm_for_each_vcpu(i, vcpu, kvm) {
if (vcpu->arch.has_run_once)
goto out_unlock;
}
--
1.9.3
next reply other threads:[~2014-11-30 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 4:18 Chen Gang [this message]
2014-11-30 10:07 ` [PATCH] kvm: arm: vgic: Let one looping code instead of two looping code Christoffer Dall
2014-11-30 10:50 ` Chen Gang
2014-11-30 11:08 ` Christoffer Dall
2014-11-30 14:21 ` Chen Gang
2014-11-30 10:50 ` Chen Gang
2014-11-30 10:52 ` 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=547A9A7C.1080508@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=christoffer.dall@linaro.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
/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