From: Auger Eric <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, peter.maydell@linaro.org,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: vijay.kilari@gmail.com, Vijaya.Kumar@cavium.com,
drjones@redhat.com, Prakash B <bjsprakash.linux@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] hw/intc/arm_gicv3_kvm: Check KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS in reset
Date: Tue, 28 Mar 2017 16:02:51 +0200 [thread overview]
Message-ID: <6799a75d-e424-c3c1-41ae-f0715f727455@redhat.com> (raw)
In-Reply-To: <1490709513-7180-1-git-send-email-eric.auger@redhat.com>
Adding Prakash B in cc too, sorry.
Vijaya, please let me know if I missed something in your original patch.
I tested GICv3 KVM save/restore with v4.11-rc4 and Prakash B use case
with 4.10 kernel.
Thanks
Eric
On 28/03/2017 15:58, Eric Auger wrote:
> KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS needs to be checked before
> attempting to read ICC_CTLR_EL1; otherwise kernel versions not
> exposing this kvm device group will be incompatible with qemu 2.9.
>
> Fixes: 07a5628 ("hw/intc/arm_gicv3_kvm: Reset GICv3 cpu interface registers")
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Reported-by: Prakash B <bjsprakash.linux@gmail.com>
>
> ---
>
> I understand the ICC_CTLR_EL1 state only is used in the put() function
> which is used for migration
> ---
> hw/intc/arm_gicv3_kvm.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
>
> diff --git a/hw/intc/arm_gicv3_kvm.c b/hw/intc/arm_gicv3_kvm.c
> index 81f0403..4c3a88e 100644
> --- a/hw/intc/arm_gicv3_kvm.c
> +++ b/hw/intc/arm_gicv3_kvm.c
> @@ -614,12 +614,6 @@ static void arm_gicv3_icc_reset(CPUARMState *env, const ARMCPRegInfo *ri)
> s = c->gic;
> cpu = ARM_CPU(c->cpu);
>
> - /* Initialize to actual HW supported configuration */
> - kvm_device_access(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS,
> - KVM_VGIC_ATTR(ICC_CTLR_EL1, cpu->mp_affinity),
> - &c->icc_ctlr_el1[GICV3_NS], false);
> -
> - c->icc_ctlr_el1[GICV3_S] = c->icc_ctlr_el1[GICV3_NS];
> c->icc_pmr_el1 = 0;
> c->icc_bpr[GICV3_G0] = GIC_MIN_BPR;
> c->icc_bpr[GICV3_G1] = GIC_MIN_BPR;
> @@ -628,6 +622,17 @@ static void arm_gicv3_icc_reset(CPUARMState *env, const ARMCPRegInfo *ri)
> c->icc_sre_el1 = 0x7;
> memset(c->icc_apr, 0, sizeof(c->icc_apr));
> memset(c->icc_igrpen, 0, sizeof(c->icc_igrpen));
> +
> + if (!kvm_device_check_attr(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS,
> + KVM_VGIC_ATTR(ICC_CTLR_EL1, cpu->mp_affinity))) {
> + return;
> + }
> + /* Initialize to actual HW supported configuration */
> + kvm_device_access(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS,
> + KVM_VGIC_ATTR(ICC_CTLR_EL1, cpu->mp_affinity),
> + &c->icc_ctlr_el1[GICV3_NS], false);
> +
> + c->icc_ctlr_el1[GICV3_S] = c->icc_ctlr_el1[GICV3_NS];
> }
>
> static void kvm_arm_gicv3_reset(DeviceState *dev)
>
next prev parent reply other threads:[~2017-03-28 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 13:58 [Qemu-devel] [PATCH] hw/intc/arm_gicv3_kvm: Check KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS in reset Eric Auger
2017-03-28 14:02 ` Auger Eric [this message]
2017-03-28 15:08 ` Vijay Kilari
2017-03-28 15:43 ` Auger Eric
2017-03-30 5:32 ` Prakash B
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=6799a75d-e424-c3c1-41ae-f0715f727455@redhat.com \
--to=eric.auger@redhat.com \
--cc=Vijaya.Kumar@cavium.com \
--cc=bjsprakash.linux@gmail.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vijay.kilari@gmail.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).