From: andre.przywara@arm.com (Andre Przywara)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/arm64: vgic: Remove unreachable irq_clear_pending
Date: Mon, 24 Nov 2014 12:04:11 +0000 [thread overview]
Message-ID: <54731EBB.5080707@arm.com> (raw)
In-Reply-To: <1416822116-9044-1-git-send-email-christoffer.dall@linaro.org>
Hej Christoffer,
On 24/11/14 09:41, Christoffer Dall wrote:
> When 'injecting' an edge-triggered interrupt with a falling edge we
> shouldn't clear the pending state on the distributor. In fact, we
> don't, because the check in vgic_validate_injection would prevent us
> from ever reaching this bit of code.
>
> Remove the unreachable snippet.
>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Acked-by: Andre Przywara <andre.przywara@arm.com>
I agree on this. Would it make sense to rewrite this function a bit to
make it more clearer what happens? I find the nesting of the
if-statements counter-intuitive: I'd prefer to first differentiate
between level and edge triggered and then only check the actual level in
the level-triggered branch. Not sure if it's worth the fuss, though.
Cheers,
Andre.
> ---
> virt/kvm/arm/vgic.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
> index 3aaca49..f45cf16 100644
> --- a/virt/kvm/arm/vgic.c
> +++ b/virt/kvm/arm/vgic.c
> @@ -1643,8 +1643,6 @@ static bool vgic_update_irq_pending(struct kvm *kvm, int cpuid,
> vgic_dist_irq_clear_level(vcpu, irq_num);
> if (!vgic_dist_irq_soft_pend(vcpu, irq_num))
> vgic_dist_irq_clear_pending(vcpu, irq_num);
> - } else {
> - vgic_dist_irq_clear_pending(vcpu, irq_num);
> }
> }
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Andre Przywara <andre.przywara@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] arm/arm64: vgic: Remove unreachable irq_clear_pending
Date: Mon, 24 Nov 2014 12:04:11 +0000 [thread overview]
Message-ID: <54731EBB.5080707@arm.com> (raw)
In-Reply-To: <1416822116-9044-1-git-send-email-christoffer.dall@linaro.org>
Hej Christoffer,
On 24/11/14 09:41, Christoffer Dall wrote:
> When 'injecting' an edge-triggered interrupt with a falling edge we
> shouldn't clear the pending state on the distributor. In fact, we
> don't, because the check in vgic_validate_injection would prevent us
> from ever reaching this bit of code.
>
> Remove the unreachable snippet.
>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Acked-by: Andre Przywara <andre.przywara@arm.com>
I agree on this. Would it make sense to rewrite this function a bit to
make it more clearer what happens? I find the nesting of the
if-statements counter-intuitive: I'd prefer to first differentiate
between level and edge triggered and then only check the actual level in
the level-triggered branch. Not sure if it's worth the fuss, though.
Cheers,
Andre.
> ---
> virt/kvm/arm/vgic.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
> index 3aaca49..f45cf16 100644
> --- a/virt/kvm/arm/vgic.c
> +++ b/virt/kvm/arm/vgic.c
> @@ -1643,8 +1643,6 @@ static bool vgic_update_irq_pending(struct kvm *kvm, int cpuid,
> vgic_dist_irq_clear_level(vcpu, irq_num);
> if (!vgic_dist_irq_soft_pend(vcpu, irq_num))
> vgic_dist_irq_clear_pending(vcpu, irq_num);
> - } else {
> - vgic_dist_irq_clear_pending(vcpu, irq_num);
> }
> }
>
>
next prev parent reply other threads:[~2014-11-24 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 9:41 [PATCH] arm/arm64: vgic: Remove unreachable irq_clear_pending Christoffer Dall
2014-11-24 9:41 ` Christoffer Dall
2014-11-24 12:04 ` Andre Przywara [this message]
2014-11-24 12:04 ` Andre Przywara
2014-11-24 12:52 ` Christoffer Dall
2014-11-24 12:52 ` Christoffer Dall
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=54731EBB.5080707@arm.com \
--to=andre.przywara@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.