mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liulongfang <liulongfang@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: <alex.williamson@redhat.com>,
	<shameerali.kolothum.thodi@huawei.com>,
	<jonathan.cameron@huawei.com>, <kvm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [PATCH 5/5] hisi_acc_vfio_pci: bugfix live migration function without VF device driver
Date: Thu, 12 Dec 2024 10:04:09 +0800	[thread overview]
Message-ID: <f35c7425-3990-97b7-09c7-065b11ef5eec@huawei.com> (raw)
In-Reply-To: <20241209135119.GB1888283@ziepe.ca>

On 2024/12/9 21:51, Jason Gunthorpe wrote:
> On Fri, Dec 06, 2024 at 05:33:12PM +0800, Longfang Liu wrote:
>> If the driver of the VF device is not loaded in the Guest OS,
>> then perform device data migration. The migrated data address will
>> be NULL.
>> The live migration recovery operation on the destination side will
>> access a null address value, which will cause access errors.
>>
>> Therefore, live migration of VMs without added VF device drivers
>> does not require device data migration.
>> In addition, when the queue address data obtained by the destination
>> is empty, device queue recovery processing will not be performed.
> 
> This seems very strange, why can't you migrate over the null DMA addr?
> Shouldn't this be fixed on the receiving side?
>

There are two parts to the process here:
First: If the source does not add the device driver in the Guest VM.
Then except the dma address is empty, other device parameters are also
empty data. Therefore, there is no need to migrate this data of the device.

Second: If the source adds the driver in the VM, but the received DMA
address is empty due to data reading or migration process. This kind of
empty address needs to be processed at the destination and cannot be
written to the device.

Thanks,
Longfang.

> Jason
> .
> 

      reply	other threads:[~2024-12-12  2:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  9:33 [PATCH 0/5] bugfix some driver issues Longfang Liu
2024-12-06  9:33 ` [PATCH 1/5] hisi_acc_vfio_pci: fix XQE dma address error Longfang Liu
2024-12-06  9:33 ` [PATCH 2/5] hisi_acc_vfio_pci: add eq and aeq interruption restore Longfang Liu
2024-12-06  9:33 ` [PATCH 3/5] hisi_acc_vfio_pci: bugfix cache write-back issue Longfang Liu
2024-12-06  9:33 ` [PATCH 4/5] hisi_acc_vfio_pci: bugfix the problem of uninstalling driver Longfang Liu
2024-12-09 13:49   ` Jason Gunthorpe
2024-12-12  1:46     ` liulongfang
2024-12-06  9:33 ` [PATCH 5/5] hisi_acc_vfio_pci: bugfix live migration function without VF device driver Longfang Liu
2024-12-09 13:51   ` Jason Gunthorpe
2024-12-12  2:04     ` liulongfang [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=f35c7425-3990-97b7-09c7-065b11ef5eec@huawei.com \
    --to=liulongfang@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=jonathan.cameron@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=shameerali.kolothum.thodi@huawei.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

all inboxes | Powered by JetHome®