From: Ani Sinha <anisinha@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, jusual@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH] acpi: pcihp: make pending delete expire in 5sec
Date: Tue, 4 Apr 2023 13:06:38 +0530 (IST) [thread overview]
Message-ID: <1de406aa-338f-277a-96a2-dcf6afbc8aec@redhat.com> (raw)
In-Reply-To: <qdzi3oh24okot23eccd6d453wehyagbxhldoss4bup2whfohfo@hkzr2p3fq6na>
On Tue, 4 Apr 2023, Gerd Hoffmann wrote:
> Hi,
>
> > > Allowing pending delete expire brings ACPI PCI hotplug on par
> > > with native PCIe unplug behavior [1] which in its turn refers
> > > back to ACPI PCI hotplug ability to repeat unplug requests.
>
> > A bit concerned about how this interacts with failover,
> > and 5sec is a lot of time that I hoped we'd avoid with acpi.
> > Any better ideas of catching such misbehaving guests?
>
> The 5sec are coming from the pcie spec: The hot-unplug request can be
> canceled within 5 seconds by pressing the button again. The problem here
> is that both hotplug and hot-unplug use the same signaling path, so we
> really have to wait the 5 seconds to avoid the OS mis-interpreting the
> button press as 'cancel' event.
>
> ACPI hotplug hasn't this problem. A unplug request is a unplug request,
For ACPI case, I think all we want is to make sure that the first unplug
event to not stick forever. A non-zero but small delay would make sure
that the first
unplug event would get cleared after that interval and subsequent unplug
events will get registered without that error.
> period. And it can't be canceled. So it should be possible to use a
> shorter period. Possibly even no delay at all.
>
> take care,
> Gerd
>
>
next prev parent reply other threads:[~2023-04-04 7:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:16 [PATCH] acpi: pcihp: make pending delete expire in 5sec Igor Mammedov
2023-04-03 17:23 ` Michael S. Tsirkin
2023-04-04 7:03 ` Gerd Hoffmann
2023-04-04 7:36 ` Ani Sinha [this message]
2023-04-04 12:40 ` Michael S. Tsirkin
2023-04-04 13:56 ` Igor Mammedov
2023-04-04 8:30 ` Igor Mammedov
2023-04-04 10:46 ` Gerd Hoffmann
2023-04-06 11:46 ` Igor Mammedov
2023-04-06 12:01 ` Gerd Hoffmann
2023-04-04 8:28 ` Igor Mammedov
2023-04-04 12:46 ` Michael S. Tsirkin
2023-04-04 14:04 ` Igor Mammedov
2023-04-04 14:10 ` Ani Sinha
2023-04-04 14:40 ` Michael S. Tsirkin
2023-04-04 14:42 ` Michael S. Tsirkin
2023-04-05 7:30 ` Igor Mammedov
2023-04-05 8:32 ` Michael S. Tsirkin
2023-04-05 9:24 ` Igor Mammedov
2023-04-05 9:59 ` Michael S. Tsirkin
2023-04-05 12:03 ` Igor Mammedov
2023-04-05 12:27 ` Michael S. Tsirkin
2023-04-05 12:32 ` Ani Sinha
2023-04-04 14:11 ` 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=1de406aa-338f-277a-96a2-dcf6afbc8aec@redhat.com \
--to=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).