From: Christoffer Dall <christoffer.dall@linaro.org>
To: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
kvm@vger.kernel.org
Subject: [PATCH v9 1/9] KVM: arm/arm64: Remove redundant preemptible checks
Date: Wed, 20 Dec 2017 12:35:58 +0100 [thread overview]
Message-ID: <20171220113606.7030-2-christoffer.dall@linaro.org> (raw)
In-Reply-To: <20171220113606.7030-1-christoffer.dall@linaro.org>
The __this_cpu_read() and __this_cpu_write() functions already implement
checks for the required preemption levels when using
CONFIG_DEBUG_PREEMPT which gives you nice error messages and such.
Therefore there is no need to explicitly check this using a BUG_ON() in
the code (which we don't do for other uses of per cpu variables either).
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
---
virt/kvm/arm/arm.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/virt/kvm/arm/arm.c b/virt/kvm/arm/arm.c
index 6b60c98a6e22..3610e132df8b 100644
--- a/virt/kvm/arm/arm.c
+++ b/virt/kvm/arm/arm.c
@@ -71,7 +71,6 @@ static DEFINE_PER_CPU(unsigned char, kvm_arm_hardware_enabled);
static void kvm_arm_set_running_vcpu(struct kvm_vcpu *vcpu)
{
- BUG_ON(preemptible());
__this_cpu_write(kvm_arm_running_vcpu, vcpu);
}
@@ -81,7 +80,6 @@ static void kvm_arm_set_running_vcpu(struct kvm_vcpu *vcpu)
*/
struct kvm_vcpu *kvm_arm_get_running_vcpu(void)
{
- BUG_ON(preemptible());
return __this_cpu_read(kvm_arm_running_vcpu);
}
--
2.14.2
next prev parent reply other threads:[~2017-12-20 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 11:35 [PATCH v9 0/9] Handle forwarded level-triggered interrupts Christoffer Dall
2017-12-20 11:35 ` Christoffer Dall [this message]
2017-12-20 11:35 ` [PATCH v9 2/9] KVM: arm/arm64: Factor out functionality to get vgic mmio requester_vcpu Christoffer Dall
2017-12-20 11:36 ` [PATCH v9 3/9] KVM: arm/arm64: Don't cache the timer IRQ level Christoffer Dall
2017-12-20 11:36 ` [PATCH v9 4/9] KVM: arm/arm64: vgic: Support level-triggered mapped interrupts Christoffer Dall
2017-12-20 11:36 ` [PATCH v9 5/9] KVM: arm/arm64: Support a vgic interrupt line level sample function Christoffer Dall
2017-12-20 11:36 ` [PATCH v9 6/9] KVM: arm/arm64: Support VGIC dist pend/active changes for mapped IRQs Christoffer Dall
2017-12-20 11:36 ` [PATCH v9 7/9] KVM: arm/arm64: Provide a get_input_level for the arch timer Christoffer Dall
2018-01-22 12:32 ` Tomasz Nowicki
2018-01-22 17:58 ` Christoffer Dall
2018-01-30 12:49 ` Christoffer Dall
2018-01-31 8:32 ` Tomasz Nowicki
2018-01-31 8:32 ` Tomasz Nowicki
2017-12-20 11:36 ` [PATCH v9 8/9] KVM: arm/arm64: Avoid work when userspace iqchips are not used Christoffer Dall
2017-12-27 16:36 ` Marc Zyngier
2018-01-02 9:09 ` Christoffer Dall
2017-12-20 11:36 ` [PATCH v9 9/9] KVM: arm/arm64: Delete outdated forwarded irq documentation Christoffer Dall
2017-12-27 16:37 ` Marc Zyngier
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=20171220113606.7030-2-christoffer.dall@linaro.org \
--to=christoffer.dall@linaro.org \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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