From: "Cédric Le Goater" <clg@kaod.org>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, yang.zhong@intel.com
Cc: pbonzini@redhat.com, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 1/5] ppc64: Express dependencies of 'pseries' and 'powernv' machines with kconfig
Date: Wed, 30 Jan 2019 12:00:39 +0100 [thread overview]
Message-ID: <381c04ec-8ec2-77d1-d3e7-403ce46f593e@kaod.org> (raw)
In-Reply-To: <1548841387-7670-2-git-send-email-thuth@redhat.com>
On 1/30/19 10:43 AM, Thomas Huth wrote:
> The POWERNV switch should always select ISA_IPMI_BT, then the other
> IPMI options are turned on automatically now.
> CONFIG_DIMM should always be selected by the pseries machine,
> which in turn depends on CONFIG_MEM_DEVICE since DIMM implements
> this interface.
> CONFIG_VIRTIO_VGA can be dropped from default-configs/ppc64-softmmu.mak
> completely since this device is already automatically enabled via
> hw/display/Kconfig now.
> CONFIG_SPAPR_RNG should stay in the ppc-softmmu.mak file since this
> is a completely optional device.
>
> Cc: Cédric Le Goater <clg@kaod.org>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> default-configs/ppc64-softmmu.mak | 7 -------
> hw/intc/Kconfig | 4 +---
> hw/mem/Kconfig | 1 +
> hw/ppc/Kconfig | 9 +++++++++
> 4 files changed, 11 insertions(+), 10 deletions(-)
>
> diff --git a/default-configs/ppc64-softmmu.mak b/default-configs/ppc64-softmmu.mak
> index a0a9151..6f8d7ea 100644
> --- a/default-configs/ppc64-softmmu.mak
> +++ b/default-configs/ppc64-softmmu.mak
> @@ -5,14 +5,7 @@ include ppc-softmmu.mak
>
> # For PowerNV
> CONFIG_POWERNV=y
> -CONFIG_IPMI=y
> -CONFIG_IPMI_LOCAL=y
> -CONFIG_IPMI_EXTERN=y
> -CONFIG_ISA_IPMI_BT=y
>
> # For pSeries
> CONFIG_PSERIES=y
> -CONFIG_VIRTIO_VGA=y
> -CONFIG_MEM_DEVICE=y
> -CONFIG_DIMM=y
> CONFIG_SPAPR_RNG=y
> diff --git a/hw/intc/Kconfig b/hw/intc/Kconfig
> index 6eea14e..1e819d0 100644
> --- a/hw/intc/Kconfig
> +++ b/hw/intc/Kconfig
> @@ -31,13 +31,11 @@ config OPENPIC_KVM
>
> config XICS
> bool
> - default y
> - depends on PSERIES
>
> config XICS_SPAPR
> bool
> default y
> - depends on PSERIES
> + depends on XICS && PSERIES
>
> config XICS_KVM
> bool
> diff --git a/hw/mem/Kconfig b/hw/mem/Kconfig
> index d1e635c..620fd4c 100644
> --- a/hw/mem/Kconfig
> +++ b/hw/mem/Kconfig
> @@ -1,5 +1,6 @@
> config DIMM
> bool
> + select MEM_DEVICE
>
> config MEM_DEVICE
> bool
> diff --git a/hw/ppc/Kconfig b/hw/ppc/Kconfig
> index b0095e1..b44e3bd 100644
> --- a/hw/ppc/Kconfig
> +++ b/hw/ppc/Kconfig
> @@ -1,11 +1,20 @@
> config PSERIES
> bool
> + select DIMM
> + select PCI
> + select VFIO
> + select XICS
Don't we want XICS_SPAPR ? or is there another toggle with KVM ?
> config SPAPR_RNG
> bool
> + depends on PSERIES
>
> config POWERNV
> bool
> + select ISA_IPMI_BT
yes.
It is possible to start a PowerNV machine without defining a
BT device but the machine relies on the BT device and the IPMI
backend attached to it to powerdown.
Ideally I would have preferred to define the device internally
in the machine and plug it on the ISA bus but I couldn't find
a way to do it cleanly.
> + select ISA_BUS
> + select MC146818RTC
> + select XICS
only for POWER8 machines. POWER9 uses XIVE.
Thanks,
C.
>
> config PPC405
> bool
>
next prev parent reply other threads:[~2019-01-30 11:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f01a301-d639-dbe7-f522-42a50e2d443e@redhat.com>
2019-01-28 15:29 ` [Qemu-devel] [PATCH] s390x: express dependencies with Kconfig Thomas Huth
2019-01-28 16:08 ` [Qemu-devel] [qemu-s390x] " Cornelia Huck
2019-01-29 9:08 ` Thomas Huth
2019-01-29 9:42 ` [Qemu-devel] [PATCH v2] " Thomas Huth
2019-01-29 9:49 ` [Qemu-devel] [qemu-s390x] " Cornelia Huck
2019-01-29 10:07 ` Paolo Bonzini
2019-01-29 11:02 ` Yang Zhong
2019-01-30 9:43 ` [Qemu-devel] [RFC PATCH 0/5] Kconfig dependencies for ppc machines Thomas Huth
2019-01-30 9:43 ` [Qemu-devel] [RFC PATCH 1/5] ppc64: Express dependencies of 'pseries' and 'powernv' machines with kconfig Thomas Huth
2019-01-30 9:57 ` Paolo Bonzini
2019-01-30 10:02 ` Thomas Huth
2019-01-30 10:15 ` Paolo Bonzini
2019-01-30 11:00 ` Cédric Le Goater [this message]
2019-01-30 11:04 ` Thomas Huth
2019-01-30 11:12 ` Cédric Le Goater
2019-01-30 9:43 ` [Qemu-devel] [RFC PATCH 2/5] ppc: Express dependencies of the 'prep' and '40p' " Thomas Huth
2019-01-30 10:17 ` Paolo Bonzini
2019-01-30 10:25 ` Thomas Huth
2019-01-30 11:02 ` Thomas Huth
2019-01-30 11:10 ` Paolo Bonzini
2019-01-30 11:09 ` Paolo Bonzini
2019-01-30 9:43 ` [Qemu-devel] [RFC PATCH 3/5] ppc: Express dependencies of the Mac " Thomas Huth
2019-01-30 10:18 ` Paolo Bonzini
2019-01-30 17:13 ` Mark Cave-Ayland
2019-01-30 17:21 ` Paolo Bonzini
2019-01-31 5:23 ` Thomas Huth
2019-01-30 9:43 ` [Qemu-devel] [RFC PATCH 4/5] ppc: Express dependencies of the Sam460EX " Thomas Huth
2019-01-30 10:18 ` Paolo Bonzini
2019-01-30 11:29 ` BALATON Zoltan
2019-01-30 12:03 ` Thomas Huth
2019-01-30 9:43 ` [Qemu-devel] [RFC PATCH 5/5] ppc: Express dependencies of the embedded " Thomas Huth
2019-01-30 10:18 ` Paolo Bonzini
2019-01-30 10:59 ` [Qemu-devel] [RFC PATCH 0/5] Kconfig dependencies for ppc machines Yang Zhong
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=381c04ec-8ec2-77d1-d3e7-403ce46f593e@kaod.org \
--to=clg@kaod.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
--cc=yang.zhong@intel.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).