From: Jason Gunthorpe <jgg@nvidia.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
alex.williamson@redhat.com, yishaih@nvidia.com,
kevin.tian@intel.com, linuxarm@huawei.com,
liulongfang@huawei.com
Subject: Re: [PATCH] hisi_acc_vfio_pci: Update migration data pointer correctly on saving/resume
Date: Mon, 20 Nov 2023 10:29:28 -0400 [thread overview]
Message-ID: <20231120142928.GC6083@nvidia.com> (raw)
In-Reply-To: <20231120091406.780-1-shameerali.kolothum.thodi@huawei.com>
On Mon, Nov 20, 2023 at 09:14:06AM +0000, Shameer Kolothum wrote:
> When the optional PRE_COPY support was added to speed up the device
> compatibility check, it failed to update the saving/resuming data
> pointers based on the fd offset. This results in migration data
> corruption and when the device gets started on the destination the
> following error is reported in some cases,
>
> [ 478.907684] arm-smmu-v3 arm-smmu-v3.2.auto: event 0x10 received:
> [ 478.913691] arm-smmu-v3 arm-smmu-v3.2.auto: 0x0000310200000010
> [ 478.919603] arm-smmu-v3 arm-smmu-v3.2.auto: 0x000002088000007f
> [ 478.925515] arm-smmu-v3 arm-smmu-v3.2.auto: 0x0000000000000000
> [ 478.931425] arm-smmu-v3 arm-smmu-v3.2.auto: 0x0000000000000000
> [ 478.947552] hisi_zip 0000:31:00.0: qm_axi_rresp [error status=0x1] found
> [ 478.955930] hisi_zip 0000:31:00.0: qm_db_timeout [error status=0x400] found
> [ 478.955944] hisi_zip 0000:31:00.0: qm sq doorbell timeout in function 2
>
> Fixes: d9a871e4a143 ("hisi_acc_vfio_pci: Introduce support for PRE_COPY state transitions")
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> ---
> drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
next prev parent reply other threads:[~2023-11-20 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 9:14 [PATCH] hisi_acc_vfio_pci: Update migration data pointer correctly on saving/resume Shameer Kolothum
2023-11-20 14:29 ` Jason Gunthorpe [this message]
2024-01-05 15:56 ` Shameerali Kolothum Thodi
2024-01-05 16:30 ` Alex Williamson
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=20231120142928.GC6083@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liulongfang@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.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).