From: Peter Maydell <peter.maydell@linaro.org>
To: Shivang Upadhyay <shivangu@linux.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, npiggin@gmail.com,
milesg@linux.ibm.com, Aditya Gupta <adityag@linux.ibm.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>,
BALATON Zoltan <balaton@eik.bme.hu>,
qemu-stable@nongnu.org
Subject: Re: [PATCH v2] ppc/pnv: fix dumpdtb option
Date: Wed, 11 Mar 2026 14:57:23 +0000 [thread overview]
Message-ID: <CAFEAcA-MHLyKvJcbSpEGQz74dgFLJm2Bhda2=xSgXigdU=32eg@mail.gmail.com> (raw)
In-Reply-To: <20260311143549.118720-1-shivangu@linux.ibm.com>
On Wed, 11 Mar 2026 at 14:36, Shivang Upadhyay <shivangu@linux.ibm.com> wrote:
>
> The '-machine dumpdtb' command line option stopped working on
> PowerPC/pnv systems after recent design change [1].
>
> Fixing this by generating fdt blob in `pnv_init`.
>
> [1] https://lore.kernel.org/qemu-devel/20250206151214.2947842-1-peter.maydell@linaro.org/
>
> Cc: Aditya Gupta <adityag@linux.ibm.com>
> Cc: Harsh Prateek Bora <harshpb@linux.ibm.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: BALATON Zoltan <balaton@eik.bme.hu>
> Cc: qemu-stable@nongnu.org
> Fixes: 8fd2518ef2f8d34 ("hw: Centralize handling of -machine dumpdtb option")
> Signed-off-by: Shivang Upadhyay <shivangu@linux.ibm.com>
>
> ---
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
next prev parent reply other threads:[~2026-03-11 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 14:35 [PATCH v2] ppc/pnv: fix dumpdtb option Shivang Upadhyay
2026-03-11 14:57 ` Peter Maydell [this message]
2026-03-11 15:04 ` Shivang Upadhyay
2026-03-13 6:15 ` Aditya Gupta
2026-03-13 6:41 ` Aditya Gupta
2026-03-13 11:20 ` Aditya Gupta
2026-03-13 16:33 ` Shivang Upadhyay
2026-03-16 6:09 ` Shivang Upadhyay
2026-03-23 23:16 ` Nathan Chancellor
2026-03-24 6:30 ` Shivang Upadhyay
2026-03-24 8:42 ` Shivang Upadhyay
2026-03-24 10:14 ` Peter Maydell
2026-03-24 10:21 ` Shivang Upadhyay
2026-03-24 10:47 ` Shivang Upadhyay
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='CAFEAcA-MHLyKvJcbSpEGQz74dgFLJm2Bhda2=xSgXigdU=32eg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=adityag@linux.ibm.com \
--cc=balaton@eik.bme.hu \
--cc=harshpb@linux.ibm.com \
--cc=milesg@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=shivangu@linux.ibm.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