From: Greg Kurz <groug@kaod.org>
To: Laurent Vivier <lvivier@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Cédric Le Goater" <clg@kaod.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 2/2] ppc/pnv: Fix PCI_EXPRESS dependency
Date: Wed, 5 Feb 2020 22:20:52 +0100 [thread overview]
Message-ID: <20200205222052.1a5cdea5@bahia.lan> (raw)
In-Reply-To: <20200205204115.555212-3-lvivier@redhat.com>
On Wed, 5 Feb 2020 21:41:15 +0100
Laurent Vivier <lvivier@redhat.com> wrote:
> When PHB4 bridge has been added, the dependencies to PCIE_PORT has been
> added to XIVE_SPAPR and indirectly to PSERIES.
> The build of the PowerNV machine is fine while we also build the PSERIES
> machine.
> If we disable the PSERIES machine, the PowerNV build fails because the
> PCI Express files are not built:
>
> /usr/bin/ld: hw/ppc/pnv.o: in function `pnv_chip_power8_pic_print_info':
> .../hw/ppc/pnv.c:623: undefined reference to `pnv_phb3_msi_pic_print_info'
> /usr/bin/ld: hw/ppc/pnv.o: in function `pnv_chip_power9_pic_print_info':
> .../hw/ppc/pnv.c:639: undefined reference to `pnv_phb4_pic_print_info'
> /usr/bin/ld: ../hw/usb/hcd-ehci-pci.o: in function `usb_ehci_pci_write_config':
> .../hw/usb/hcd-ehci-pci.c:129: undefined reference to `pci_default_write_config'
> /usr/bin/ld: ../hw/usb/hcd-ehci-pci.o: in function `usb_ehci_pci_realize':
> .../hw/usb/hcd-ehci-pci.c:68: undefined reference to `pci_allocate_irq'
> /usr/bin/ld: .../hw/usb/hcd-ehci-pci.c:72: undefined reference to `pci_register_bar'
> /usr/bin/ld: ../hw/usb/hcd-ehci-pci.o:(.data.rel+0x50): undefined reference to `vmstate_pci_device'
>
> This patch fixes the problem by adding needed dependencies to POWERNV.
>
> Fixes: 4f9924c4d4cf ("ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge")
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/ppc/Kconfig | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ppc/Kconfig b/hw/ppc/Kconfig
> index 354828bf132f..3e11d0b53e11 100644
> --- a/hw/ppc/Kconfig
> +++ b/hw/ppc/Kconfig
> @@ -29,6 +29,10 @@ config POWERNV
> select XICS
> select XIVE
> select FDT_PPC
> + select PCI
Is it needed since PCI_EXPRESS already selects PCI in hw/pci/Kconfig ?
Apart from that:
Reviewed-by: Greg Kurz <groug@kaod.org>
> + select PCI_EXPRESS
> + select MSI_NONBROKEN
> + select PCIE_PORT
>
> config PPC405
> bool
> @@ -135,8 +139,6 @@ config XIVE_SPAPR
> default y
> depends on PSERIES
> select XIVE
> - select PCI
> - select PCIE_PORT
>
> config XIVE_KVM
> bool
next prev parent reply other threads:[~2020-02-05 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 20:41 [PATCH 0/2] ppc/pnv: fix build dependencies Laurent Vivier
2020-02-05 20:41 ` [PATCH 1/2] qtest: Fix rtas dependencies Laurent Vivier
2020-02-05 20:46 ` Thomas Huth
2020-02-05 20:49 ` Laurent Vivier
2020-02-05 20:41 ` [PATCH 2/2] ppc/pnv: Fix PCI_EXPRESS dependency Laurent Vivier
2020-02-05 21:20 ` Greg Kurz [this message]
2020-02-05 23:17 ` Laurent Vivier
2020-02-06 6:31 ` Thomas Huth
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=20200205222052.1a5cdea5@bahia.lan \
--to=groug@kaod.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).