From: Laurent Vivier <lvivier@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Julia Suvorova <jusual@redhat.com>,
qemu-devel@nongnu.org, Ani Sinha <ani@anisinha.ca>,
Igor Mammedov <imammedo@redhat.com>,
Jens Freimann <jfreimann@redhat.com>
Subject: Re: [PATCH v3] failover: fix unplug pending detection
Date: Fri, 1 Oct 2021 13:01:37 +0200 [thread overview]
Message-ID: <0eeefb15-1b41-076c-7dd4-ca5fc78eefa9@redhat.com> (raw)
In-Reply-To: <20211001104514.46bhlpenx4rz2qnm@sirius.home.kraxel.org>
On 01/10/2021 12:45, Gerd Hoffmann wrote:
> On Fri, Oct 01, 2021 at 10:25:02AM +0200, Laurent Vivier wrote:
>> Failover needs to detect the end of the PCI unplug to start migration
>> after the VFIO card has been unplugged.
>>
>> To do that, a flag is set in pcie_cap_slot_unplug_request_cb() and reset in
>> pcie_unplug_device().
>
>> + /*
>> + * pending_deleted_event is used by virtio-net failover to detect the
>> + * end of the unplug operation, the flag is set to false in
>> + * acpi_pcihp_eject_slot() when the operation is completed.
>> + */
>> + pdev->qdev.pending_deleted_event = true;
>
> This has the side effect of blocking a second 'device_del' command.
This problem is not introduced by this patch as it only adds the code we already have in
PCIe Native hotplug to ACPI hotplug (but see below).
> So, in case the first time didn't work (for example due to the guest not
> listening because grub just doesn't do that), you can try a second time
> once the linux kernel is up'n'running.
>
> I suspect this patch will break that (didn't actually test though).
I think the solution to this problem is to not check for pending_deleted_event value in
qmp_device_del().
But this has been explicitly added by:
commit cce8944cc9efab47d4bf29cfffb3470371c3541b
Author: Julia Suvorova <jusual@redhat.com>
Date: Thu Feb 20 17:55:56 2020 +0100
qdev-monitor: Forbid repeated device_del
Device unplug can be done asynchronously. Thus, sending the second
device_del before the previous unplug is complete may lead to
unexpected results. On PCIe devices, this cancels the hot-unplug
process.
Signed-off-by: Julia Suvorova <jusual@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20200220165556.39388-1-jusual@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
So do you mean ACPI differs from PCIe Native hotplug in this case?
Thanks,
Laurent
next prev parent reply other threads:[~2021-10-01 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 8:25 [PATCH v3] failover: fix unplug pending detection Laurent Vivier
2021-10-01 10:45 ` Gerd Hoffmann
2021-10-01 10:48 ` Daniel P. Berrangé
2021-10-01 11:01 ` Laurent Vivier [this message]
2021-10-01 12:49 ` Gerd Hoffmann
2021-10-01 13:17 ` Ani Sinha
2021-10-01 15:19 ` Ani Sinha
2021-10-05 15:14 ` Michael S. Tsirkin
2021-10-05 16:01 ` Laurent Vivier
2021-10-06 5:53 ` Ani Sinha
2021-10-18 7:19 ` Laurent Vivier
2021-10-18 8:27 ` Michael S. Tsirkin
2021-11-18 9:15 ` Laurent Vivier
2021-11-18 10:04 ` Ani Sinha
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=0eeefb15-1b41-076c-7dd4-ca5fc78eefa9@redhat.com \
--to=lvivier@redhat.com \
--cc=ani@anisinha.ca \
--cc=berrange@redhat.com \
--cc=imammedo@redhat.com \
--cc=jfreimann@redhat.com \
--cc=jusual@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).