All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, mtosatti@redhat.com,
	marcel.apfelbaum@gmail.com, jon.grimm@amd.com,
	santosh.shukla@amd.com, vasant.hegde@amd.com, Wei.Huang2@amd.com,
	bsd@redhat.com, berrange@redhat.com, joao.m.martins@oracle.com,
	alejandro.j.jimenez@oracle.com
Subject: Re: [PATCH v3 0/2] hw/i386/amd_iommu: Add migration support
Date: Thu, 20 Feb 2025 18:21:32 -0500	[thread overview]
Message-ID: <20250220182112-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250212054450.578449-1-suravee.suthikulpanit@amd.com>

On Wed, Feb 12, 2025 at 05:44:48AM +0000, Suravee Suthikulpanit wrote:
> Currently, amd-iommu device does not support migration. This series addresses
> an issue due hidden AMDVI-PCI device enumeration. Then introduces migratable
> VMStateDescription, which saves necessary parameters for the device.
> 
> Changes from v2:
> (https://lore.kernel.org/all/20250206051856.323651-1-suravee.suthikulpanit@amd.com)
>   * Add patch 1/2


Fails build on 32 bit:

https://gitlab.com/mstredhat/qemu/-/jobs/9202574769


In file included from ../include/qemu/osdep.h:53,
                 from ../hw/i386/amd_iommu.c:23:
../include/qemu/compiler.h:70:35: error: invalid operands to binary - (have ‘uint64_t *’ {aka ‘long long unsigned int *’} and ‘size_t *’ {aka ‘unsigned int *’})
   70 | #define type_check(t1,t2) ((t1*)0 - (t2*)0)
      |                                   ^
../include/migration/vmstate.h:269:6: note: in expansion of macro ‘type_check’
  269 |      type_check(_type, typeof_field(_state, _field)))
      |      ^~~~~~~~~~
../include/migration/vmstate.h:320:21: note: in expansion of macro ‘vmstate_offset_value’
  320 |     .offset       = vmstate_offset_value(_state, _field, _type),     \
      |                     ^~~~~~~~~~~~~~~~~~~~
../include/migration/vmstate.h:853:5: note: in expansion of macro ‘VMSTATE_SINGLE_TEST’
  853 |     VMSTATE_SINGLE_TEST(_field, _state, NULL, _version, _info, _type)
      |     ^~~~~~~~~~~~~~~~~~~
../include/migration/vmstate.h:903:5: note: in expansion of macro ‘VMSTATE_SINGLE’
  903 |     VMSTATE_SINGLE(_f, _s, _v, vmstate_info_uint64, uint64_t)
      |     ^~~~~~~~~~~~~~
../include/migration/vmstate.h:937:5: note: in expansion of macro ‘VMSTATE_UINT64_V’
  937 |     VMSTATE_UINT64_V(_f, _s, 0)
      |     ^~~~~~~~~~~~~~~~
../hw/i386/amd_iommu.c:1635:7: note: in expansion of macro ‘VMSTATE_UINT64’
 1635 |       VMSTATE_UINT64(devtab_len, AMDVIState),
      |       ^~~~~~~~~~~~~~


> Suravee Suthikulpanit (2):
>   hw/i386/amd_iommu: Isolate AMDVI-PCI from amd-iommu device to allow
>     full control over the PCI device creation
>   hw/i386/amd_iommu: Allow migration when explicitly create the
>     AMDVI-PCI device
> 
>  hw/i386/acpi-build.c |   8 ++--
>  hw/i386/amd_iommu.c  | 111 +++++++++++++++++++++++++++++++++----------
>  hw/i386/amd_iommu.h  |   3 +-
>  3 files changed, 91 insertions(+), 31 deletions(-)
> 
> -- 
> 2.34.1



      parent reply	other threads:[~2025-02-20 23:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  5:44 [PATCH v3 0/2] hw/i386/amd_iommu: Add migration support Suravee Suthikulpanit
2025-02-12  5:44 ` [PATCH v3 1/2] hw/i386/amd_iommu: Isolate AMDVI-PCI from amd-iommu device to allow full control over the PCI device creation Suravee Suthikulpanit
2025-02-21  0:38   ` Michael S. Tsirkin
2025-02-25 13:39     ` Suthikulpanit, Suravee
2025-02-12  5:44 ` [PATCH v3 2/2] hw/i386/amd_iommu: Allow migration when explicitly create the AMDVI-PCI device Suravee Suthikulpanit
2025-02-20 23:21 ` Michael S. Tsirkin [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=20250220182112-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Wei.Huang2@amd.com \
    --cc=alejandro.j.jimenez@oracle.com \
    --cc=berrange@redhat.com \
    --cc=bsd@redhat.com \
    --cc=joao.m.martins@oracle.com \
    --cc=jon.grimm@amd.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=santosh.shukla@amd.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.