qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Michael Roth" <michael.roth@amd.com>,
	qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Ani Sinha" <ani@anisinha.ca>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Jens Freimann" <jfreimann@redhat.com>
Subject: Re: [PATCH v5 3/4] failover: fix unplug pending detection
Date: Wed, 8 Dec 2021 08:50:34 +0100	[thread overview]
Message-ID: <6764b29d-3885-ec0e-0b90-f0c05a544571@redhat.com> (raw)
In-Reply-To: <20211208023603-mutt-send-email-mst@kernel.org>

On 08/12/2021 08.36, Michael S. Tsirkin wrote:
> On Fri, Nov 19, 2021 at 10:07:17AM +0100, 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().
>>
>> But since
>>      17858a169508 ("hw/acpi/ich9: Set ACPI PCI hot-plug as default on Q35")
>> we have switched to ACPI unplug and these functions are not called anymore
>> and the flag not set. So failover migration is not able to detect if card
>> is really unplugged and acts as it's done as soon as it's started. So it
>> doesn't wait the end of the unplug to start the migration. We don't see any
>> problem when we test that because ACPI unplug is faster than PCIe native
>> hotplug and when the migration really starts the unplug operation is
>> already done.
>>
>> See c000a9bd06ea ("pci: mark device having guest unplug request pending")
>>      a99c4da9fc2a ("pci: mark devices partially unplugged")
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> Reviewed-by: Ani Sinha <ani@anisinha.ca>
> 
> Hmm.  I think this one may be needed for this release actually.
> Isolate from testing changes and repost?

You merged it already here:

  https://gitlab.com/qemu-project/qemu/-/commit/9323f892b39d133eb6

so we should be fine :-)

  Thomas



  reply	other threads:[~2021-12-08  7:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19  9:07 [PATCH v5 0/4] tests/qtest: add some tests for virtio-net failover Laurent Vivier
2021-11-19  9:07 ` [PATCH v5 1/4] qtest/libqos: add a function to initialize secondary PCI buses Laurent Vivier
2021-11-19  9:07 ` [PATCH v5 2/4] tests/qtest: add some tests for virtio-net failover Laurent Vivier
2021-11-19  9:07 ` [PATCH v5 3/4] failover: fix unplug pending detection Laurent Vivier
2021-12-08  7:36   ` Michael S. Tsirkin
2021-12-08  7:50     ` Thomas Huth [this message]
2021-12-08 10:44       ` Ani Sinha
2021-12-08 11:11       ` Michael S. Tsirkin
2021-11-19  9:07 ` [PATCH v5 4/4] tests/libqtest: update virtio-net failover test Laurent Vivier
2021-12-08  7:34 ` [PATCH v5 0/4] tests/qtest: add some tests for virtio-net failover Michael S. Tsirkin

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=6764b29d-3885-ec0e-0b90-f0c05a544571@redhat.com \
    --to=thuth@redhat.com \
    --cc=ani@anisinha.ca \
    --cc=berrange@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jfreimann@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).