From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Vijay Kilari <vijay.kilari@gmail.com>,
"Kumar, Vijaya" <Vijaya.Kumar@cavium.com>,
Andrew Jones <drjones@redhat.com>, Peter Xu <peterx@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [RFC v2 3/3] hw/intc/arm_gicv3_its: Allow save/restore
Date: Mon, 13 Mar 2017 19:03:41 +0100 [thread overview]
Message-ID: <CAFEAcA97hCS-bbKDV+w2G3yRunUm=QpsA+8Bqp9YNaa_VtMP-w@mail.gmail.com> (raw)
In-Reply-To: <1488800894-22421-4-git-send-email-eric.auger@redhat.com>
On 6 March 2017 at 12:48, Eric Auger <eric.auger@redhat.com> wrote:
> We change the restoration priority of both the GICv3 and ITS. The
> GICv3 must be restored before the ITS and the ITS needs to be restored
> before PCIe devices since it translates their MSI transactions.
> We typically observe the virtio-pci-net device sending MSI transactions
> very early (even before the first vcpu run) which looks weird. It
> appears that not servicing those transactions cause the virtio-pci-net
> to stall.
This does seem rather weird and worth closer investigation.
A stopped VM ought IMHO to be completely stopped, not still
doing things...
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>
> ---
>
> v1 -> v2:
> - handle case where migrate_add_blocker fails
> - add comments along with ITS and GICv3 migration priorities
> ---
> hw/intc/arm_gicv3_common.c | 1 +
> hw/intc/arm_gicv3_its_common.c | 3 ++-
> hw/intc/arm_gicv3_its_kvm.c | 23 +++++++++++------------
> include/migration/vmstate.h | 2 ++
> 4 files changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/hw/intc/arm_gicv3_common.c b/hw/intc/arm_gicv3_common.c
> index c6493d6..4228b7c 100644
> --- a/hw/intc/arm_gicv3_common.c
> +++ b/hw/intc/arm_gicv3_common.c
> @@ -145,6 +145,7 @@ static const VMStateDescription vmstate_gicv3 = {
> .minimum_version_id = 1,
> .pre_save = gicv3_pre_save,
> .post_load = gicv3_post_load,
> + .priority = MIG_PRI_GICV3,
> .fields = (VMStateField[]) {
> VMSTATE_UINT32(gicd_ctlr, GICv3State),
> VMSTATE_UINT32_ARRAY(gicd_statusr, GICv3State, 2),
> diff --git a/hw/intc/arm_gicv3_its_common.c b/hw/intc/arm_gicv3_its_common.c
> index 75b9f04..854709f 100644
> --- a/hw/intc/arm_gicv3_its_common.c
> +++ b/hw/intc/arm_gicv3_its_common.c
> @@ -48,7 +48,8 @@ static const VMStateDescription vmstate_its = {
> .name = "arm_gicv3_its",
> .pre_save = gicv3_its_pre_save,
> .post_load = gicv3_its_post_load,
> - .unmigratable = true,
> + .unmigratable = false,
unmigratable = false is the default, so we can just delete the line.
> + .priority = MIG_PRI_GICV3_ITS,
> .fields = (VMStateField[]) {
> VMSTATE_UINT32(ctlr, GICv3ITSState),
> VMSTATE_UINT64(cbaser, GICv3ITSState),
> diff --git a/hw/intc/arm_gicv3_its_kvm.c b/hw/intc/arm_gicv3_its_kvm.c
> index 45e57d6..3bd2873 100644
> --- a/hw/intc/arm_gicv3_its_kvm.c
> +++ b/hw/intc/arm_gicv3_its_kvm.c
> @@ -76,18 +76,6 @@ static void kvm_arm_its_realize(DeviceState *dev, Error **errp)
> GICv3ITSState *s = ARM_GICV3_ITS_COMMON(dev);
> Error *local_err = NULL;
>
> - /*
> - * Block migration of a KVM GICv3 ITS device: the API for saving and
> - * restoring the state in the kernel is not yet available
> - */
> - error_setg(&s->migration_blocker, "vITS migration is not implemented");
> - migrate_add_blocker(s->migration_blocker, &local_err);
> - if (local_err) {
> - error_propagate(errp, local_err);
> - error_free(s->migration_blocker);
> - return;
> - }
> -
> s->dev_fd = kvm_create_device(kvm_state, KVM_DEV_TYPE_ARM_VGIC_ITS, false);
> if (s->dev_fd < 0) {
> error_setg_errno(errp, -s->dev_fd, "error creating in-kernel ITS");
> @@ -104,6 +92,17 @@ static void kvm_arm_its_realize(DeviceState *dev, Error **errp)
>
> gicv3_its_init_mmio(s, NULL);
>
> + if (!kvm_device_check_attr(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_ITS_REGS,
> + GITS_CTLR)) {
> + error_setg(&s->migration_blocker, "vITS migration is not implemented");
I think we should specifically say that it's the host kernel
that doesn't support ITS migration (ie not QEMU that's missing
support).
The GICv3 uses the message
"This operating system kernel does not support vGICv3 migration"
which is slightly odd phrasing but I guess we should follow that.
> + migrate_add_blocker(s->migration_blocker, &local_err);
> + if (local_err) {
> + error_propagate(errp, local_err);
> + error_free(s->migration_blocker);
> + return;
> + }
> + }
> +
> kvm_msi_use_devid = true;
> kvm_gsi_direct_mapping = false;
> kvm_msi_via_irqfd_allowed = kvm_irqfds_enabled();
> diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
> index f2dbf84..8dab9c7 100644
> --- a/include/migration/vmstate.h
> +++ b/include/migration/vmstate.h
> @@ -198,6 +198,8 @@ enum VMStateFlags {
> typedef enum {
> MIG_PRI_DEFAULT = 0,
> MIG_PRI_IOMMU, /* Must happen before PCI devices */
> + MIG_PRI_GICV3_ITS, /* Must happen before PCI devices */
> + MIG_PRI_GICV3, /* Must happen before the ITS */
> MIG_PRI_MAX,
> } MigrationPriority;
>
> --
> 2.5.5
>
thanks
-- PMM
next prev parent reply other threads:[~2017-03-13 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 11:48 [Qemu-devel] [RFC v2 0/3] vITS save/restore Eric Auger
2017-03-06 11:48 ` [Qemu-devel] [RFC v2 1/3] linux-headers: Update for " Eric Auger
2017-03-06 11:48 ` [Qemu-devel] [RFC v2 2/3] hw/intc/arm_gicv3_its: Implement state save/restore Eric Auger
2017-03-13 17:58 ` Peter Maydell
2017-03-16 15:26 ` Auger Eric
2017-03-06 11:48 ` [Qemu-devel] [RFC v2 3/3] hw/intc/arm_gicv3_its: Allow save/restore Eric Auger
2017-03-13 18:03 ` Peter Maydell [this message]
2017-03-16 15:28 ` Auger Eric
2017-03-27 9:43 ` Auger Eric
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='CAFEAcA97hCS-bbKDV+w2G3yRunUm=QpsA+8Bqp9YNaa_VtMP-w@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=Vijaya.Kumar@cavium.com \
--cc=christoffer.dall@linaro.org \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).