From: Peter Maydell <peter.maydell@linaro.org>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Damien Hedde <damien.hedde@greensocs.com>,
Francisco Eduardo Iglesias <figlesia@xilinx.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Edgar Iglesias <edgar.iglesias@xilinx.com>,
Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>,
Francisco Iglesias <frasse.iglesias@gmail.com>,
Alistair Francis <alistair@alistair23.me>,
Richard Henderson <richard.henderson@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
KONRAD Frederic <frederic.konrad@adacore.com>,
qemu-arm <qemu-arm@nongnu.org>,
Luc Michel <luc.michel@greensocs.com>
Subject: Re: [PATCH v1 0/1] intc/arm_gic: Fix gic_irq_signaling_enabled() for vCPUs
Date: Thu, 7 Jan 2021 12:02:24 +0000 [thread overview]
Message-ID: <CAFEAcA8HDAWqQtGuc6XQNP5o1SbXpp4D+98pyHr3Td2a03ZVpQ@mail.gmail.com> (raw)
In-Reply-To: <20201214222154.3480243-1-edgar.iglesias@gmail.com>
On Mon, 14 Dec 2020 at 22:21, Edgar E. Iglesias
<edgar.iglesias@gmail.com> wrote:
>
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
>
> Hi,
>
> Found this while debugging an issue with lockups during boot of
> Linux on Xen.
>
> In the particular setup, I'm running without EL3 firmware so group0
> interrupts are disabled on the physical interface and enabled on the
> virtual interface.
>
> Looks like we're checking the wrong CPU_CTLR reg for vCPUs. This fixes
> the problem on my side.
Applied to target-arm.next, thanks.
-- PMM
prev parent reply other threads:[~2021-01-07 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 22:21 [PATCH v1 0/1] intc/arm_gic: Fix gic_irq_signaling_enabled() for vCPUs Edgar E. Iglesias
2020-12-14 22:21 ` [PATCH v1 1/1] " Edgar E. Iglesias
2020-12-14 23:20 ` Philippe Mathieu-Daudé
2020-12-15 10:28 ` Luc Michel
2021-01-07 12:02 ` Peter Maydell [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=CAFEAcA8HDAWqQtGuc6XQNP5o1SbXpp4D+98pyHr3Td2a03ZVpQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair@alistair23.me \
--cc=damien.hedde@greensocs.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=figlesia@xilinx.com \
--cc=frasse.iglesias@gmail.com \
--cc=frederic.konrad@adacore.com \
--cc=luc.michel@greensocs.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sai.pavan.boddu@xilinx.com \
--cc=sstabellini@kernel.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).