From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, anisinha@redhat.com, jusual@redhat.com,
kraxel@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH] acpi: pcihp: make pending delete expire in 5sec
Date: Wed, 5 Apr 2023 05:59:06 -0400 [thread overview]
Message-ID: <20230405055833-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230405112416.38e83b0c@imammedo.users.ipa.redhat.com>
On Wed, Apr 05, 2023 at 11:24:16AM +0200, Igor Mammedov wrote:
> > > PS:
> > > See commit message, Windows is not affected as it doesn't
> > > clear GPE status bits during ACPI initialization
> > > (at least the one version I've tested with, and I won't bet
> > > on this with other versions or staying this way)
> >
> > So I am saying linux should match windows. Clearing GPE
> > is a bad idea as you then miss events.
>
> I'd say it depends on if guest OS is able to handle hot[un]plug
> at boot time when it enables GPE handlers (or any other time).
> (My point of view here, it's a guest OS policy and management
> layer should know what installed guest is capable of and what
> quirks to use with it)
>
> I'll try to send a kernel patch to remove GPEx.status clearing,
> though it might be more complex than it seems,
> hence I'm quite sceptical about it.
In the world of ACPI, windows is basically the gold standard,
whatever it does linux has to do ;)
--
MST
next prev parent reply other threads:[~2023-04-05 9:59 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
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 [this message]
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=20230405055833-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@redhat.com \
--cc=kraxel@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).