From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
peter.maydell@linaro.org
Cc: maz@kernel.org, drjones@redhat.com
Subject: [RFC 0/2] hw/arm/virt: kvm: allow gicv3 by default if host does not support v2
Date: Wed, 26 Feb 2020 18:04:58 +0100 [thread overview]
Message-ID: <20200226170500.17028-1-eric.auger@redhat.com> (raw)
At the moment if the end-user does not specify the gic-version along
with KVM acceleration, v2 is set by default. However most of the
systems now have GICv3 and sometimes they do not support GICv2
compatibility. In that case we end up with this error:
qemu-system-aarch64: PMU: KVM_SET_DEVICE_ATTR: Invalid argument
qemu-system-aarch64: failed to set irq for PMU
and qemu aborts.
This patch keeps the default v2 selection in all cases except
in the KVM accelerated mode when the host does not support v2.
This case did not work anyway so we do not break any compatibility.
Now we get v3 selected in such a case. Also if the end-user explicitly
sets v2 whereas this latter is not supported, we also are
informed that v2 is not selected by thos host instead of getting the
above PMU related message.
Best Regards
Eric
This series can be found at:
https://github.com/eauger/qemu/tree/gic_version_rfc_v1
Eric Auger (2):
target/arm/kvm: Let kvm_arm_vgic_probe() return a bitmap
hw/arm/virt: kvm: allow gicv3 by default if host does not support v2
hw/arm/virt.c | 41 +++++++++++++++++++++++++++++++++++++++--
include/hw/arm/virt.h | 1 +
target/arm/kvm.c | 14 ++++++++------
target/arm/kvm_arm.h | 3 +++
4 files changed, 51 insertions(+), 8 deletions(-)
--
2.20.1
next reply other threads:[~2020-02-26 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 17:04 Eric Auger [this message]
2020-02-26 17:04 ` [RFC 1/2] target/arm/kvm: Let kvm_arm_vgic_probe() return a bitmap Eric Auger
2020-02-26 17:05 ` [RFC 2/2] hw/arm/virt: kvm: allow gicv3 by default if host does not support v2 Eric Auger
2020-02-26 18:42 ` Andrew Jones
2020-02-27 8:12 ` Auger Eric
2020-02-27 8:48 ` Andrew Jones
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=20200226170500.17028-1-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=maz@kernel.org \
--cc=peter.maydell@linaro.org \
--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).