From: David Gibson <david@gibson.dropbear.id.au>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] ppc/xics: Fix stale irq->status bits after get
Date: Mon, 1 May 2017 16:13:37 +1000 [thread overview]
Message-ID: <20170501061337.GO13773@umbus.fritz.box> (raw)
In-Reply-To: <20170427063153.GB11487@tungsten.ozlabs.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
On Thu, Apr 27, 2017 at 04:31:53PM +1000, Sam Bobroff wrote:
> ics_get_kvm_state() "or"s set bits into irq->status but does not mask
> out clear bits.
>
> Correct this by initializing the IRQ status to zero before adding bits
> to it.
>
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
This definitely looks like a bugfix, applied to ppc-for-2.10.
> ---
> hw/intc/xics_kvm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/intc/xics_kvm.c b/hw/intc/xics_kvm.c
> index 42e0e0ef84..03c1fc77cb 100644
> --- a/hw/intc/xics_kvm.c
> +++ b/hw/intc/xics_kvm.c
> @@ -213,6 +213,7 @@ static void ics_get_kvm_state(ICSState *ics)
> irq->priority = irq->saved_priority;
> }
>
> + irq->status = 0;
> if (state & KVM_XICS_PENDING) {
> if (state & KVM_XICS_LEVEL_SENSITIVE) {
> irq->status |= XICS_STATUS_ASSERTED;
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-05-01 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1493274659.git.sam.bobroff@au1.ibm.com>
2017-04-27 6:31 ` [Qemu-devel] [PATCH 1/2] ppc/xics: Fix stale irq->status bits after get Sam Bobroff
2017-05-01 6:13 ` David Gibson [this message]
2017-04-27 6:32 ` [Qemu-devel] [PATCH 2/2] ppc/xics: preserve P and Q bits for KVM IRQs Sam Bobroff
2017-05-01 6:45 ` David Gibson
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=20170501061337.GO13773@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.bobroff@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).