From: Jason Gunthorpe <jgg@ziepe.ca>
To: Longfang Liu <liulongfang@huawei.com>
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 4/5] hisi_acc_vfio_pci: bugfix the problem of uninstalling driver
Date: Mon, 9 Dec 2024 09:49:53 -0400 [thread overview]
Message-ID: <20241209134953.GA1888283@ziepe.ca> (raw)
In-Reply-To: <20241206093312.57588-5-liulongfang@huawei.com>
On Fri, Dec 06, 2024 at 05:33:11PM +0800, Longfang Liu wrote:
> In a live migration scenario. If the number of VFs at the
> destination is greater than the source, the recovery operation
> will fail and qemu will not be able to complete the process and
> exit after shutting down the device FD.
>
> This will cause the driver to be unable to be unloaded normally due
> to abnormal reference counting of the live migration driver caused
> by the abnormal closing operation of fd.
>
> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
> ---
> drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 1 +
> 1 file changed, 1 insertion(+)
This one needs a fixes line and probably cc stable
Jason
next prev parent reply other threads:[~2024-12-09 13:49 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 [this message]
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
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=20241209134953.GA1888283@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alex.williamson@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liulongfang@huawei.com \
--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®