From: Christoffer Dall <christoffer.dall@linaro.org>
To: Johan Karlsson <Johan.Karlsson@enea.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu arm gic assert failed.
Date: Thu, 13 Nov 2014 16:30:10 +0100 [thread overview]
Message-ID: <CAMJs5B-ST36jMjJU9d=PU_W5WvuU2W-vqM-dwM-HzacvyMWZAw@mail.gmail.com> (raw)
In-Reply-To: <5006DF1F5103294E8DA02CC4C71B1BF8085C0D7F@SESTOEX04.enea.se>
On Thu, Nov 13, 2014 at 4:25 PM, Johan Karlsson <Johan.Karlsson@enea.com> wrote:
>> -----Original Message-----
>> From: Christoffer Dall [mailto:christoffer.dall@linaro.org]
>> Sent: den 13 november 2014 15:28
>> On Thu, Nov 13, 2014 at 1:44 PM, Johan Karlsson
>> <Johan.Karlsson@enea.com> wrote:
>> > Hi,
>> > Enabled DEBUG_GIC in arm_gic.c
>> >
>> > Use case:
>> > Core0 wakes up core1 using irq and then core1 acks and runs eoi until it
>> gets 0x3ff.
>> > Note that core1 do not have interrupts enabled and does this in SVC.
>> >
>> > From what I can see s->current_pending[1] isn't updated in gic_update
>> because the following
>> > if (!s->enabled || !s->cpu_enabled[cpu]) {
>> > qemu_irq_lower(s->parent_irq[cpu]);
>> > return;
>> > }
>> > Is true for core0 after the first ack from core1 causing gic_update to return
>> before updating core1.
>> >
>> It was recently discussed on a previous thread that this is a bug in the QEMU,
>> the return statement above should be a 'continue;'
>>
>> Does that solve your issue?
>>
>> -Christoffer
>
> Yes I tried that and it works, however I didn't analyse if it was correct or not.
as far as I can tell, it is correct.
> But it didn't feel right to return from a function that loops over all cores based on a state of one core.
>
Exactly, care to send a patch to qemu-devel?
-Christoffer
prev parent reply other threads:[~2014-11-13 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 12:44 [Qemu-devel] qemu arm gic assert failed Johan Karlsson
2014-11-13 14:28 ` Christoffer Dall
2014-11-13 15:25 ` Johan Karlsson
2014-11-13 15:30 ` 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='CAMJs5B-ST36jMjJU9d=PU_W5WvuU2W-vqM-dwM-HzacvyMWZAw@mail.gmail.com' \
--to=christoffer.dall@linaro.org \
--cc=Johan.Karlsson@enea.com \
--cc=qemu-devel@nongnu.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 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).