From: Christoffer Dall <cdall@linaro.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Christoffer Dall <christoffer.dall@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: arm/arm64: VGIC: extend !vgic_is_initialized guard
Date: Mon, 20 Nov 2017 12:23:06 +0100 [thread overview]
Message-ID: <20171120112306.GG28855@cbox> (raw)
In-Reply-To: <20171117175821.23250-1-andre.przywara@arm.com>
Hi Andre,
On Fri, Nov 17, 2017 at 05:58:21PM +0000, Andre Przywara wrote:
> Commit f39d16cbabf9 ("KVM: arm/arm64: Guard kvm_vgic_map_is_active against
> !vgic_initialized") introduced a check whether the VGIC has been
> initialized before accessing the spinlock and the VGIC data structure.
> However the vgic_get_irq() call in the variable declaration sneaked
> through the net, so lets make sure that this also gets called only after
> we actually allocated the arrays this function accesses.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> virt/kvm/arm/vgic/vgic.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/virt/kvm/arm/vgic/vgic.c b/virt/kvm/arm/vgic/vgic.c
> index e54ef2fdf73d..967983a33ab2 100644
> --- a/virt/kvm/arm/vgic/vgic.c
> +++ b/virt/kvm/arm/vgic/vgic.c
> @@ -786,13 +786,14 @@ void vgic_kick_vcpus(struct kvm *kvm)
>
> bool kvm_vgic_map_is_active(struct kvm_vcpu *vcpu, unsigned int virt_irq)
> {
> - struct vgic_irq *irq = vgic_get_irq(vcpu->kvm, vcpu, virt_irq);
> + struct vgic_irq *irq;
> bool map_is_active;
> unsigned long flags;
>
> if (!vgic_initialized(vcpu->kvm))
> return false;
>
> + irq = vgic_get_irq(vcpu->kvm, vcpu, virt_irq);
> spin_lock_irqsave(&irq->irq_lock, flags);
> map_is_active = irq->hw && irq->active;
> spin_unlock_irqrestore(&irq->irq_lock, flags);
> --
> 2.14.1
>
As explained in the other e-mail this isn't actually strictly necessary
anymore, but I think our current appraoch of "how do we handle calls
from generic code the VGIC when the VGIC potentially hasn't been
initialized yet?" is to have an initialized check on most entry points
to the VGIC, unless strictly performance sensitive.
Therefore:
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
prev parent reply other threads:[~2017-11-20 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 17:58 [PATCH] KVM: arm/arm64: VGIC: extend !vgic_is_initialized guard Andre Przywara
2017-11-20 8:12 ` Auger Eric
2017-11-20 9:12 ` Auger Eric
2017-11-20 11:23 ` Christoffer Dall [this message]
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=20171120112306.GG28855@cbox \
--to=cdall@linaro.org \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--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