From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Revert "hw/pci: disable pci-bridge's shpc by default"
Date: Wed, 10 May 2017 17:38:45 +0200 [thread overview]
Message-ID: <fc62fe0c-01b3-8744-64f4-d03a2adf06f2@redhat.com> (raw)
In-Reply-To: <20170510092903.23649-1-marcel@redhat.com>
On 10/05/2017 11:29, Marcel Apfelbaum wrote:
> +++ 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, false),
> + PCI_BRIDGE_DEV_F_SHPC_REQ, true),
> DEFINE_PROP_END_OF_LIST(),
> };
>
> diff --git a/include/hw/compat.h b/include/hw/compat.h
> index 846b90e..eff021f 100644
> --- a/include/hw/compat.h
> +++ b/include/hw/compat.h
> @@ -18,10 +18,6 @@
> .property = "old-multiple-chip-handling",\
> .value = "on",\
> },{\
> - .driver = "pci-bridge",\
> - .property = "shpc",\
> - .value = "on",\
> - },{\
Unless we make a conscious decision to break PCI bridge backwards
compatibility, you now have to disable it for 2.9 and leave this
HW_COMPAT_2_8 hunk intact. Peter Xu has a patch to add the 2.10 machine
types.
Paolo
> .driver = TYPE_PCI_DEVICE,\
> .property = "x-pcie-extcap-init",\
> .value = "off",\
> -- 2.9.3
next prev parent reply other threads:[~2017-05-10 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 9:29 [Qemu-devel] [PATCH] Revert "hw/pci: disable pci-bridge's shpc by default" Marcel Apfelbaum
2017-05-10 15:38 ` Paolo Bonzini [this message]
2017-05-10 17:06 ` Marcel Apfelbaum
2017-05-10 18:24 ` 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=fc62fe0c-01b3-8744-64f4-d03a2adf06f2@redhat.com \
--to=pbonzini@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).