From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] pci: Skip power-off reset when pending unplug
Date: Thu, 23 Dec 2021 08:11:32 +0100 [thread overview]
Message-ID: <20211223071132.fpbyug2afss4jdjd@sirius.home.kraxel.org> (raw)
In-Reply-To: <20211222120809.3f28f44b.alex.williamson@redhat.com>
> > > > So I am not sure how to fix the assignment issues as I'm not sure how do
> > > > they trigger, but here is a wild idea: maybe it should support an API
> > > > for starting reset asynchronously, then if the following access is
> > > > trying to reset again that second reset can just be skipped, while any
> > > > other access will stall.
> > >
> > > As above, there's not a concurrency problem, so I don't see how an
> > > async API buys us anything.
> >
> > Well unplug resets the device again, right? Why is that reset not
> > problematic and this one is?
>
> It has the same issue, but there's no log message generated that
> worries QE into marking this as a regression. Obviously the ideal
> outcome would be that we could reset the device under these conditions,
> but to this point we've only managed to introduce "try" semantics to
> the functions to prevent deadlock. As this is a condition induced by
> corner case admin device handling, we've so far considered the reset
> failure acceptable. Thanks,
Maybe it makes sense to move the check for pending removal into the vfio
reset handler then, and either skip logging an error or skip reset
altogether?
take care,
Gerd
prev parent reply other threads:[~2021-12-23 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 18:26 [PATCH] pci: Skip power-off reset when pending unplug Alex Williamson
2021-12-20 23:03 ` Michael S. Tsirkin
2021-12-21 16:36 ` Alex Williamson
2021-12-21 23:40 ` Michael S. Tsirkin
2021-12-22 19:08 ` Alex Williamson
2021-12-22 20:48 ` Michael S. Tsirkin
2021-12-22 23:10 ` Alex Williamson
2021-12-23 13:33 ` Michael S. Tsirkin
2022-01-05 19:17 ` Alex Williamson
2021-12-23 7:11 ` Gerd Hoffmann [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=20211223071132.fpbyug2afss4jdjd@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).