qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, anisinha@redhat.com, jusual@redhat.com,
	pbonzini@redhat.com
Subject: Re: [PATCH] acpi: pcihp: make pending delete expire in 5sec
Date: Tue, 4 Apr 2023 10:30:55 +0200	[thread overview]
Message-ID: <20230404103055.11f2de56@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <qdzi3oh24okot23eccd6d453wehyagbxhldoss4bup2whfohfo@hkzr2p3fq6na>

On Tue, 4 Apr 2023 09:03:59 +0200
Gerd Hoffmann <kraxel@redhat.com> 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.

Any pointer to spec?
Does it apply to SHPC too?
(/me thinking about moving pending_delete check to PCIe only code)

> 
> ACPI hotplug hasn't this problem.  A unplug request is a unplug request,
> 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
> 



  parent reply	other threads:[~2023-04-04  8:31 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
2023-04-04 12:40       ` Michael S. Tsirkin
2023-04-04 13:56         ` Igor Mammedov
2023-04-04  8:30     ` Igor Mammedov [this message]
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=20230404103055.11f2de56@imammedo.users.ipa.redhat.com \
    --to=imammedo@redhat.com \
    --cc=anisinha@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).