qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@csgraf.de>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH 0/2] hw/arm/virt: Handle HVF in finalize_gic_version()
Date: Wed, 21 Dec 2022 00:04:12 +0100	[thread overview]
Message-ID: <20221220230414.47876-1-agraf@csgraf.de> (raw)

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.

Alex

Alexander Graf (2):
  hw/arm/virt: Consolidate GIC finalize logic
  hw/arm/virt: Make accels in GIC finalize logic explicit

 hw/arm/virt.c         | 199 ++++++++++++++++++++++--------------------
 include/hw/arm/virt.h |  12 +--
 2 files changed, 110 insertions(+), 101 deletions(-)

-- 
2.37.1 (Apple Git-137.1)



             reply	other threads:[~2022-12-20 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 23:04 Alexander Graf [this message]
2022-12-20 23:04 ` [PATCH 1/2] hw/arm/virt: Consolidate GIC finalize logic Alexander Graf
2022-12-21  3:35   ` Zenghui Yu via
2022-12-21  9:28     ` Alexander Graf
2022-12-20 23:04 ` [PATCH 2/2] hw/arm/virt: Make accels in GIC finalize logic explicit Alexander Graf
2022-12-21  3:28 ` [PATCH 0/2] hw/arm/virt: Handle HVF in finalize_gic_version() Zenghui Yu via
  -- strict thread matches above, loose matches on Subject: below --
2022-12-21  9:28 Alexander Graf

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=20221220230414.47876-1-agraf@csgraf.de \
    --to=agraf@csgraf.de \
    --cc=peter.maydell@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).