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, Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] ppc/pnv: generate dtb after machine initialization is complete
Date: Tue, 24 Mar 2026 13:54:04 +0000 [thread overview]
Message-ID: <CAFEAcA_fvj_LZu+BMqW-LNtK1k-agsumTUu6wR0ZKOJJ6R0EOQ@mail.gmail.com> (raw)
In-Reply-To: <20260324135026.247418-1-shivangu@linux.ibm.com>
On Tue, 24 Mar 2026 at 13:51, Shivang Upadhyay <shivangu@linux.ibm.com> wrote:
>
> Currently, the machine dtb is generated in pnv_init(), before all devices
> are fully initialized. This can result in an incomplete dtb for the system,
> as seen in bug [1].
>
> Fix this by deferring dtb generation until machine initialization is complete,
> using the machine_init_done_notifier hook.
>
> [1] https://lore.kernel.org/all/20260323231612.GA2637687@ax162/
>
> Cc: Aditya Gupta <adityag@linux.ibm.com>
> Cc: Harsh Prateek Bora <harshpb@linux.ibm.com>
> Cc: BALATON Zoltan <balaton@eik.bme.hu>
> Cc: qemu-stable@nongnu.org
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Fixes: a16d4c2f162a86d ("ppc/pnv: fix 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-24 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 13:50 [PATCH] ppc/pnv: generate dtb after machine initialization is complete Shivang Upadhyay
2026-03-24 13:54 ` Peter Maydell [this message]
2026-03-24 19:22 ` Nathan Chancellor
2026-03-26 11:16 ` Aditya Gupta
2026-03-26 11:25 ` Peter Maydell
2026-03-26 11:55 ` Aditya Gupta
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_fvj_LZu+BMqW-LNtK1k-agsumTUu6wR0ZKOJJ6R0EOQ@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=nathan@kernel.org \
--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