All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: peter.maydell@linaro.org
Cc: lvivier@redhat.com, aik@ozlabs.ru, qemu-devel@nongnu.org,
	groug@kaod.org, qemu-ppc@nongnu.org, clg@kaod.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PULL 12/13] ppc/pnv: activate the "dumpdtb" option on the powernv machine
Date: Wed, 12 Jun 2019 15:49:28 +1000	[thread overview]
Message-ID: <20190612054929.21136-13-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20190612054929.21136-1-david@gibson.dropbear.id.au>

From: Cédric Le Goater <clg@kaod.org>

This is a good way to debug the DT creation for current PowerNV
machines and new ones to come.

Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20190606174732.13051-1-clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 hw/ppc/pnv.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
index 046f0a83c8..ed68924667 100644
--- a/hw/ppc/pnv.c
+++ b/hw/ppc/pnv.c
@@ -23,6 +23,7 @@
 #include "sysemu/sysemu.h"
 #include "sysemu/numa.h"
 #include "sysemu/cpus.h"
+#include "sysemu/device_tree.h"
 #include "hw/hw.h"
 #include "target/ppc/cpu.h"
 #include "qemu/log.h"
@@ -554,6 +555,7 @@ static void pnv_reset(void)
     /* Pack resulting tree */
     _FDT((fdt_pack(fdt)));
 
+    qemu_fdt_dumpdtb(fdt, fdt_totalsize(fdt));
     cpu_physical_memory_write(PNV_FDT_ADDR, fdt, fdt_totalsize(fdt));
 }
 
-- 
2.21.0



  parent reply	other threads:[~2019-06-12  5:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  5:49 [Qemu-devel] [PULL 00/13] ppc-for-4.1 queue 20190612 David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 01/13] spapr_pci: Improve error message David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 02/13] target/ppc: Fix lxvw4x, lxvh8x and lxvb16x David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 03/13] spapr: Clean up device node name generation for PCI devices David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 04/13] spapr: Clean up device tree construction " David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 05/13] spapr: Clean up dt creation for PCI buses David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 06/13] spapr: Clean up spapr_drc_populate_dt() David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 07/13] spapr: Clean up DRC index construction David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 08/13] spapr: Don't use bus number for building DRC ids David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 09/13] spapr: Direct all PCI hotplug to host bridge, rather than P2P bridge David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 10/13] spapr: Allow hot plug/unplug of PCI bridges and devices under PCI bridges David Gibson
2019-06-12  5:49 ` [Qemu-devel] [PULL 11/13] target/ppc: Use tcg_gen_gvec_bitsel David Gibson
2019-06-12  5:49 ` David Gibson [this message]
2019-06-12  5:49 ` [Qemu-devel] [PULL 13/13] ppc/xive: Make XIVE generate the proper interrupt types David Gibson
2019-06-12 15:40 ` [Qemu-devel] [PULL 00/13] ppc-for-4.1 queue 20190612 Peter Maydell

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=20190612054929.21136-13-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=aik@ozlabs.ru \
    --cc=clg@kaod.org \
    --cc=groug@kaod.org \
    --cc=lvivier@redhat.com \
    --cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.