qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com, laine@redhat.com, mst@redhat.com, marcel@redhat.com
Subject: [Qemu-devel] [PATCH] hw/pci: disable pci-bridge's shpc by default
Date: Wed,  2 Nov 2016 17:16:42 +0200	[thread overview]
Message-ID: <1478099802-14188-1-git-send-email-marcel@redhat.com> (raw)

The shpc component is optional while  ACPI hotplug is used
for hot-plugging PCI devices into a PCI-PCI bridge.
Disabling the shpc by default will make slot 0 usable at boot time
and not only for hot-plug, without loosing any functionality.
Older machines will have shpc enabled for compatibility reasons.

Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
---
 hw/pci-bridge/pci_bridge_dev.c | 2 +-
 include/hw/compat.h            | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/hw/pci-bridge/pci_bridge_dev.c b/hw/pci-bridge/pci_bridge_dev.c
index 5dbd933..647ad80 100644
--- a/hw/pci-bridge/pci_bridge_dev.c
+++ b/hw/pci-bridge/pci_bridge_dev.c
@@ -163,7 +163,7 @@ static Property pci_bridge_dev_properties[] = {
     DEFINE_PROP_ON_OFF_AUTO(PCI_BRIDGE_DEV_PROP_MSI, PCIBridgeDev, msi,
                             ON_OFF_AUTO_AUTO),
     DEFINE_PROP_BIT(PCI_BRIDGE_DEV_PROP_SHPC, PCIBridgeDev, flags,
-                    PCI_BRIDGE_DEV_F_SHPC_REQ, true),
+                    PCI_BRIDGE_DEV_F_SHPC_REQ, false),
     DEFINE_PROP_END_OF_LIST(),
 };
 
diff --git a/include/hw/compat.h b/include/hw/compat.h
index 0f06e11..388b7ec 100644
--- a/include/hw/compat.h
+++ b/include/hw/compat.h
@@ -18,6 +18,10 @@
         .driver   = "intel-iommu",\
         .property = "x-buggy-eim",\
         .value    = "true",\
+    },{\
+        .driver   = "pci-bridge",\
+        .property = "shpc",\
+        .value    = "on",\
     },
 
 #define HW_COMPAT_2_6 \
-- 
2.5.5

             reply	other threads:[~2016-11-02 15:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 15:16 Marcel Apfelbaum [this message]
2016-11-02 16:01 ` [Qemu-devel] [PATCH] hw/pci: disable pci-bridge's shpc by default Laine Stump
2016-11-03 11:08   ` Marcel Apfelbaum
2016-11-03 15:24     ` Laine Stump
2016-11-03 16:43       ` Marcel Apfelbaum
2016-11-03 19:09         ` Eduardo Habkost
2016-11-03  4:18 ` Michael S. Tsirkin
2016-11-03 11:05   ` Marcel Apfelbaum
2016-11-03 19:40     ` Michael S. Tsirkin
2016-11-05 16:46       ` Marcel Apfelbaum
2016-11-16 16:44         ` Andrew Jones
2016-11-16 17:05           ` Marcel Apfelbaum
2016-11-18 15:52             ` Andrew Jones
2016-11-18 15:55               ` Michael S. Tsirkin
2016-11-22 17:26               ` Marcel Apfelbaum
2016-11-22 20:25                 ` Laurent Vivier
2016-11-23 11:08                   ` Marcel Apfelbaum
2016-11-24  4:06                     ` David Gibson
2016-11-24  9:39                       ` Marcel Apfelbaum
2016-11-25  4:14                         ` David Gibson
2016-11-22 17:47               ` Michael S. Tsirkin
2017-01-10  3:48 ` 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=1478099802-14188-1-git-send-email-marcel@redhat.com \
    --to=marcel@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=laine@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).