From: Peter Maydell <peter.maydell@linaro.org>
To: Joelle van Dyne <j@getutm.app>
Cc: Alexander Graf <agraf@csgraf.de>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH] hvf: arm: Add support for GICv3
Date: Fri, 10 Mar 2023 09:49:07 +0000 [thread overview]
Message-ID: <CAFEAcA-40Qt5XCK7_M6kdCYNWy+nrkx2CKgrBuDYRmGA_u_oOA@mail.gmail.com> (raw)
In-Reply-To: <CA+E+eSC-Q9SvTR29qbYRMPfo10xhM9OtaXZNO6iJp0UAA96kCg@mail.gmail.com>
On Fri, 10 Mar 2023 at 04:55, Joelle van Dyne <j@getutm.app> wrote:
>
> On Mon, Dec 19, 2022 at 2:08 PM Alexander Graf <agraf@csgraf.de> wrote:
> >
> > We currently only support GICv2 emulation. To also support GICv3, we will
> > need to pass a few system registers into their respective handler functions.
> >
> > This patch adds support for HVF to call into the TCG callbacks for GICv3
> > system register handlers. This is safe because the GICv3 TCG code is generic
> > as long as we limit ourselves to EL0 and EL1 - which are the only modes
> > supported by HVF.
> >
> > To make sure nobody trips over that, we also annotate callbacks that don't
> > work in HVF mode, such as EL state change hooks.
> >
> > With GICv3 support in place, we can run with more than 8 vCPUs.
> >
> > Signed-off-by: Alexander Graf <agraf@csgraf.de>
> > ---
>
> Tested-by: Joelle van Dyne <j@getutm.app>
Just FYI, this patch is already upstream (commit a2260983c6553).
-- PMM
prev parent reply other threads:[~2023-03-10 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 22:08 [PATCH] hvf: arm: Add support for GICv3 Alexander Graf
2022-12-20 7:14 ` Zenghui Yu via
2022-12-20 7:37 ` Alexander Graf
2022-12-20 14:13 ` Zenghui Yu via
2023-01-06 16:37 ` Peter Maydell
2023-01-28 22:32 ` Alexander Graf
2023-03-10 4:55 ` Joelle van Dyne
2023-03-10 9:49 ` 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-40Qt5XCK7_M6kdCYNWy+nrkx2CKgrBuDYRmGA_u_oOA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@csgraf.de \
--cc=j@getutm.app \
--cc=qemu-arm@nongnu.org \
--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).