From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, marcel.a@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/9] pc: acpi: decribe bridge device as not hotpluggable
Date: Tue, 9 Dec 2014 14:51:59 +0200 [thread overview]
Message-ID: <20141209125159.GA4674@redhat.com> (raw)
In-Reply-To: <20141209124527.0d433241@nial.usersys.redhat.com>
On Tue, Dec 09, 2014 at 12:45:27PM +0100, Igor Mammedov wrote:
> On Tue, 9 Dec 2014 12:34:02 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Tue, Dec 09, 2014 at 11:27:16AM +0100, Igor Mammedov wrote:
> > > On Mon, 8 Dec 2014 21:13:25 +0200
> > > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > >
> > > > On Mon, Dec 08, 2014 at 04:08:01PM +0000, Igor Mammedov wrote:
> > > > > when bridge hotplug is disabled, i.e. for machine
> > > > > types less then 2.0, bridge device was created as
> > > > > hotpluggable by mistake since commit 133a2da.
> > > > >
> > > > > Fix it by just creating it as a present device.
> > > > >
> > > > > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > > >
> > > > What exactly is the problem here?
> > > > It seems that such bridge is hotpluggable, even though
> > > > e.g. windows guests lacks drivers to support this.
> > > before 133a2da slot with existing at startup bridge weren't
> > > marked as hotpluggable nor described in SSDT. But after
> > > 133a2da it's described as hotpluggable slot for compat
> > > machines (2.0 and lower) which doesn't match with original
> > > behavior.
> > >
> > > Also Marcel mentioned that bridges could be hotpluggable
> > > but that they should not be hot-UNpluggable.
> >
> > OK so is there some guest that's confused?
> > What's the bug?
> It allows to do eject on bridge when it shouldn't.
I'm not sure it shouldn't. Assuming guest supports SHPC, eject on such a
bridge might well work correctly.
> I don't know about consequences of it,
> it's better not to allow invalid action in the first place.
>
>
> >
> > > >
> > > >
> > > > > ---
> > > > > hw/i386/acpi-build.c | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> > > > > index b37a397..1fb92e5 100644
> > > > > --- a/hw/i386/acpi-build.c
> > > > > +++ b/hw/i386/acpi-build.c
> > > > > @@ -913,7 +913,7 @@ static void build_pci_bus_end(PCIBus *bus, void *bus_state)
> > > > > }
> > > > > }
> > > > >
> > > > > - if (!dc->hotpluggable || bridge_in_acpi) {
> > > > > + if (!dc->hotpluggable || pc->is_bridge) {
> > > > > clear_bit(slot, slot_hotplug_enable);
> > > > > }
> > > > > }
> > > > > --
> > > > > 1.8.3.1
next prev parent reply other threads:[~2014-12-09 12:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 16:07 [Qemu-devel] [PATCH 0/9] pc: acpi: various fixes and cleanups Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 1/9] pc: acpi: fix WindowsXP BSOD when memory hotplug is enabled Igor Mammedov
2014-12-08 20:57 ` Michael S. Tsirkin
2014-12-09 10:05 ` Igor Mammedov
2014-12-09 10:33 ` Michael S. Tsirkin
2014-12-08 16:08 ` [Qemu-devel] [PATCH 2/9] pc: acpi: decribe bridge device as not hotpluggable Igor Mammedov
2014-12-08 19:13 ` Michael S. Tsirkin
2014-12-09 10:27 ` Igor Mammedov
2014-12-09 10:34 ` Michael S. Tsirkin
2014-12-09 11:45 ` Igor Mammedov
2014-12-09 12:51 ` Michael S. Tsirkin [this message]
2014-12-09 12:57 ` Igor Mammedov
2014-12-09 13:16 ` Michael S. Tsirkin
2014-12-09 13:08 ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 3/9] pc: acpi-build: cleanup AcpiPmInfo initialization Igor Mammedov
2014-12-08 21:03 ` Michael S. Tsirkin
2014-12-09 10:29 ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 4/9] acpi: build_append_nameseg(): add padding if necessary Igor Mammedov
2014-12-08 21:15 ` Michael S. Tsirkin
2014-12-09 10:32 ` Igor Mammedov
2014-12-09 10:38 ` Michael S. Tsirkin
2014-12-09 12:55 ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 5/9] acpi: move generic aml building helpers into dedictated file Igor Mammedov
2014-12-08 20:43 ` Michael S. Tsirkin
2014-12-09 10:37 ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 6/9] acpi: add build_append_namestring() helper Igor Mammedov
2014-12-08 20:21 ` Michael S. Tsirkin
2014-12-09 10:39 ` Igor Mammedov
2014-12-09 12:02 ` Michael S. Tsirkin
2014-12-09 12:59 ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 7/9] acpi: replace opencoded notify codes with named values Igor Mammedov
2014-12-08 20:54 ` Michael S. Tsirkin
2014-12-09 10:59 ` Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 8/9] acpi: drop min-bytes in build_package() Igor Mammedov
2014-12-08 16:08 ` [Qemu-devel] [PATCH 9/9] pc: acpi-build: replace recursive PCI bus tree generation with loop based Igor Mammedov
2014-12-08 20:43 ` Michael S. Tsirkin
2014-12-09 14:01 ` Igor Mammedov
2014-12-09 14:29 ` Michael S. Tsirkin
2014-12-11 11:09 ` [Qemu-devel] [PATCH V2 9/9] pc: acpi-build: simplify PCI bus tree generation Igor Mammedov
2014-12-08 20:43 ` [Qemu-devel] [PATCH 0/9] pc: acpi: various fixes and cleanups 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=20141209125159.GA4674@redhat.com \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel.a@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).