From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Alexander Graf <agraf@csgraf.de>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Zenghui Yu <yuzenghui@huawei.com>,
Eric Auger <eric.auger@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH v3 0/2] hw/arm/virt: Handle HVF in finalize_gic_version()
Date: Fri, 3 Feb 2023 10:24:06 +0000 [thread overview]
Message-ID: <CAFEAcA_nxgdj99=+q_X5mKDaEisbWrC9BgqzcK3uciGWGpjF2Q@mail.gmail.com> (raw)
In-Reply-To: <d4ce9573-6f8c-1970-a2c5-f798fa8403dd@linaro.org>
On Fri, 3 Feb 2023 at 07:07, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>
> Hi Peter,
>
> On 2/2/23 18:57, Peter Maydell wrote:
> > On Fri, 23 Dec 2022 at 09:01, Alexander Graf <agraf@csgraf.de> wrote:
> >>
> >> The finalize_gic_version() function tries to determine which GIC version
> >> the current accelerator / host combination supports. During the initial
> >> HVF porting efforts, I didn't realize that I also had to touch this
> >> function. Then Zenghui brought up this function as reply to my HVF GICv3
> >> enablement patch - and boy it is a mess.
> >>
> >> This patch set cleans up all of the GIC finalization so that we can
> >> easily plug HVF in and also hopefully will have a better time extending
> >> it in the future. As second step, it explicitly adds HVF support and
> >> fails loudly for any unsupported accelerators.
> > Applied to target-arm.next, thanks.
>
> Did you squash the changes mentioned here?
> https://lore.kernel.org/qemu-devel/3278ab81-ccdc-9ccc-e504-dca757db5658@linaro.org/
Yes, I found those when I noticed the patch didn't pass 'make check' :-)
-- PMM
prev parent reply other threads:[~2023-02-03 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 9:01 [PATCH v3 0/2] hw/arm/virt: Handle HVF in finalize_gic_version() Alexander Graf
2022-12-23 9:01 ` [PATCH v3 1/2] hw/arm/virt: Consolidate GIC finalize logic Alexander Graf
2022-12-23 12:30 ` Cornelia Huck
2022-12-23 16:37 ` Alexander Graf
2023-01-11 13:35 ` Zenghui Yu via
2022-12-23 9:01 ` [PATCH v3 2/2] hw/arm/virt: Make accels in GIC finalize logic explicit Alexander Graf
2023-01-11 13:35 ` Zenghui Yu via
2023-01-17 7:34 ` Philippe Mathieu-Daudé
2022-12-24 23:38 ` [PATCH v3 0/2] hw/arm/virt: Handle HVF in finalize_gic_version() Richard Henderson
2023-01-24 16:47 ` Peter Maydell
2023-02-02 17:57 ` Peter Maydell
2023-02-03 7:07 ` Philippe Mathieu-Daudé
2023-02-03 10:24 ` 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='CAFEAcA_nxgdj99=+q_X5mKDaEisbWrC9BgqzcK3uciGWGpjF2Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=agraf@csgraf.de \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yuzenghui@huawei.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).