[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v3 00/20] GICv3 emulation

From: Laszlo Ersek
Subject: Re: [Qemu-devel] [PATCH v3 00/20] GICv3 emulation
Date: Tue, 21 Jun 2016 21:45:32 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1

On 06/21/16 19:21, Peter Maydell wrote:
> On 21 June 2016 at 18:18, Andrew Jones <address@hidden> wrote:
>> Why oh why does mutt ask me who to CC after composing the mail instead
>> of before (after is when I've forgotten...) Maybe there's some config
>> I can change. OK, this time with Ard really on CC.
> Heh. Let me repeat my other message:
> The GICv3 emulation is in upstream QEMU master, so use that.
> Don't use the 'staging' branch in my personal git tree, that is
> "whatever random pull request I am currently testing" and therefore
> can be arbitrarily busted...
> and add a note I forgot to mention: my primary hypothesis is that
> the problem here is "guest does not write to the GICD_IGROUPR and
> GICR_IGROUPR registers to program the interrupts it's using as
> group 1, but still expects to get IRQs rather than FIQs".

... and it (or whatever else is the root cause) seems to manifest in
either the Stall() UEFI boot service, or in UEFI timer events. (This
seems to follow from the last debug log entry from Shannon:


... Just to make it clear: does it reproduce with KVM? Or is that
untested perhaps (due to lack of GICv3 hardware e.g.)?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]