From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] ppc/pnv: Remove the XICSFabric Interface from the POWER9 machine
Date: Fri, 4 Oct 2019 10:25:45 +1000 [thread overview]
Message-ID: <20191004002545.GA27597@umbus.fritz.box> (raw)
In-Reply-To: <20191003143617.21682-1-clg@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 3087 bytes --]
On Thu, Oct 03, 2019 at 04:36:17PM +0200, Cédric Le Goater wrote:
> The POWER8 PowerNV machine needs to implement a XICSFabric interface
> as this is the POWER8 interrupt controller model. But the POWER9
> machine uselessly inherits of XICSFabric from the common PowerNV
> machine definition.
>
> Open code machine definitions to have a better control on the
> different interfaces each machine should define.
>
> Fixes: f30c843ced50 ("ppc/pnv: Introduce PowerNV machines with fixed CPU models")
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Applied to ppc-for-4.2, thanks.
> ---
> hw/ppc/pnv.c | 31 ++++++++++++++-----------------
> 1 file changed, 14 insertions(+), 17 deletions(-)
>
> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> index 77a86c6a2301..7cf64b6d2533 100644
> --- a/hw/ppc/pnv.c
> +++ b/hw/ppc/pnv.c
> @@ -1485,23 +1485,21 @@ static void pnv_machine_class_init(ObjectClass *oc, void *data)
> .parent = TYPE_PNV9_CHIP, \
> }
>
> -#define DEFINE_PNV_MACHINE_TYPE(cpu, class_initfn) \
> - { \
> - .name = MACHINE_TYPE_NAME(cpu), \
> - .parent = TYPE_PNV_MACHINE, \
> - .instance_size = sizeof(PnvMachineState), \
> - .instance_init = pnv_machine_instance_init, \
> - .class_init = class_initfn, \
> - .interfaces = (InterfaceInfo[]) { \
> - { TYPE_XICS_FABRIC }, \
> - { TYPE_INTERRUPT_STATS_PROVIDER }, \
> - { }, \
> - }, \
> - }
> -
> static const TypeInfo types[] = {
> - DEFINE_PNV_MACHINE_TYPE("powernv8", pnv_machine_power8_class_init),
> - DEFINE_PNV_MACHINE_TYPE("powernv9", pnv_machine_power9_class_init),
> + {
> + .name = MACHINE_TYPE_NAME("powernv9"),
> + .parent = TYPE_PNV_MACHINE,
> + .class_init = pnv_machine_power9_class_init,
> + },
> + {
> + .name = MACHINE_TYPE_NAME("powernv8"),
> + .parent = TYPE_PNV_MACHINE,
> + .class_init = pnv_machine_power8_class_init,
> + .interfaces = (InterfaceInfo[]) {
> + { TYPE_XICS_FABRIC },
> + { },
> + },
> + },
> {
> .name = TYPE_PNV_MACHINE,
> .parent = TYPE_MACHINE,
> @@ -1510,7 +1508,6 @@ static const TypeInfo types[] = {
> .instance_init = pnv_machine_instance_init,
> .class_init = pnv_machine_class_init,
> .interfaces = (InterfaceInfo[]) {
> - { TYPE_XICS_FABRIC },
> { TYPE_INTERRUPT_STATS_PROVIDER },
> { },
> },
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-10-04 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 14:36 [PATCH] ppc/pnv: Remove the XICSFabric Interface from the POWER9 machine Cédric Le Goater
2019-10-04 0:25 ` David Gibson [this message]
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=20191004002545.GA27597@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).