From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: Aditya Gupta <adityag@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>,
"Sourabh Jain" <sourabhjain@linux.ibm.com>,
"Mahesh J Salgaonkar" <mahesh@linux.ibm.com>,
"Hari Bathini" <hbathini@linux.ibm.com>
Subject: Re: [PATCH 3/7] hw/ppc: Handle stash command in PowerNV SBE
Date: Tue, 11 Mar 2025 10:20:58 +0530 [thread overview]
Message-ID: <59df1008-2127-4ae4-b8e7-72334c58f12e@linux.ibm.com> (raw)
In-Reply-To: <20250217071934.86131-4-adityag@linux.ibm.com>
On 2/17/25 12:49, Aditya Gupta wrote:
> Earlier since the SBE_CMD_STASH_MPIPL_CONFIG command was not handled, so
> skiboot used to not get any response from SBE:
>
> [ 106.350742821,3] SBE: Message timeout [chip id = 0], cmd = d7, subcmd = 7
> [ 106.352067746,3] SBE: Failed to send stash MPIPL config [chip id = 0x0, rc = 254]
>
> Fix this by handling the command in PowerNV SBE, and sending a response so
> skiboot knows SBE has handled the STASH command
>
> The stashed skiboot base is later used to access the relocated MDST/MDDT
> tables when MPIPL is implemented.
>
> The purpose of stashing relocated base address is explained in following
> skiboot commit:
>
> author Vasant Hegde <hegdevasant@linux.vnet.ibm.com> Fri Jul 12 16:47:51 2019 +0530
> committer Oliver O'Halloran <oohall@gmail.com> Thu Aug 15 17:53:39 2019 +1000
>
> SBE: Send OPAL relocated base address to SBE
>
> OPAL relocates itself during boot. During memory preserving IPL hostboot needs
> to access relocated OPAL base address to get MDST, MDDT tables. Hence send
> relocated base address to SBE via 'stash MPIPL config' chip-op. During next
> IPL SBE will send stashed data to hostboot... so that hostboot can access
> these data.
>
> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
> ---
> hw/ppc/pnv_sbe.c | 25 +++++++++++++++++++++++++
> include/hw/ppc/pnv_sbe.h | 3 +++
> 2 files changed, 28 insertions(+)
>
> diff --git a/hw/ppc/pnv_sbe.c b/hw/ppc/pnv_sbe.c
> index a6bf13650f2d..79818177fc36 100644
> --- a/hw/ppc/pnv_sbe.c
> +++ b/hw/ppc/pnv_sbe.c
> @@ -82,6 +82,8 @@
> #define SBE_CONTROL_REG_S0 PPC_BIT(14)
> #define SBE_CONTROL_REG_S1 PPC_BIT(15)
>
> +static uint64_t mpipl_skiboot_base = 0x30000000 /*default SKIBOOT_BASE*/;
> +
> static void pnv_sbe_set_host_doorbell(PnvSBE *sbe, uint64_t val)
> {
> val &= SBE_HOST_RESPONSE_MASK; /* Is this right? What does HW do? */
> @@ -281,6 +283,29 @@ static void do_sbe_msg(PnvSBE *sbe)
> timer_del(sbe->timer);
> }
> break;
> + case SBE_CMD_STASH_MPIPL_CONFIG:
> + /* key = sbe->mbox[1] */
> + switch (sbe->mbox[1]) {
> + case SBE_STASH_KEY_SKIBOOT_BASE:
> + mpipl_skiboot_base = sbe->mbox[2];
> + qemu_log_mask(LOG_UNIMP,
> + "Stashing skiboot base: 0x%lx\n", mpipl_skiboot_base);
> +
> + /*
> + * Set the response register.
> + *
> + * Currently setting the same sequence number in
> + * response as we got in the request.
> + */
> + sbe->mbox[4] = sbe->mbox[0]; /* sequence number */
> + pnv_sbe_set_host_doorbell(sbe,
> + sbe->host_doorbell | SBE_HOST_RESPONSE_WAITING);
> +
> + break;
> + default:
> + qemu_log_mask(LOG_UNIMP, "SBE Unimplemented command: 0x%x\n", cmd);
Unimplemented SBE_CMD_STASH_MPIPL_CONFIG key ?
> + }
> + break;
> default:
> qemu_log_mask(LOG_UNIMP, "SBE Unimplemented command: 0x%x\n", cmd);
> }
> diff --git a/include/hw/ppc/pnv_sbe.h b/include/hw/ppc/pnv_sbe.h
> index b6b378ad14c7..f6cbcf990ed9 100644
> --- a/include/hw/ppc/pnv_sbe.h
> +++ b/include/hw/ppc/pnv_sbe.h
> @@ -53,4 +53,7 @@ struct PnvSBEClass {
> const MemoryRegionOps *xscom_mbox_ops;
> };
>
> +/* Helper to access stashed SKIBOOT_BASE */
> +bool pnv_sbe_mpipl_skiboot_base(void);
> +
> #endif /* PPC_PNV_SBE_H */
next prev parent reply other threads:[~2025-03-11 4:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 7:19 [PATCH 0/7] Implement MPIPL for PowerNV Aditya Gupta
2025-02-17 7:19 ` [PATCH 1/7] hw/ppc: Log S0/S1 Interrupt triggers by OPAL Aditya Gupta
2025-03-11 4:38 ` Harsh Prateek Bora
2025-03-13 18:43 ` Aditya Gupta
2025-02-17 7:19 ` [PATCH 2/7] hw/ppc: Implement S0 SBE interrupt as cpu_pause then host reset Aditya Gupta
2025-03-11 4:45 ` Harsh Prateek Bora
2025-03-13 18:45 ` Aditya Gupta
2025-02-17 7:19 ` [PATCH 3/7] hw/ppc: Handle stash command in PowerNV SBE Aditya Gupta
2025-03-11 4:50 ` Harsh Prateek Bora [this message]
2025-03-13 18:46 ` Aditya Gupta
2025-02-17 7:19 ` [PATCH 4/7] hw/ppc: Add MDST/MDDT/MDRT table structures and offsets Aditya Gupta
2025-03-11 5:11 ` Harsh Prateek Bora
2025-03-13 18:50 ` Aditya Gupta
2025-02-17 7:19 ` [PATCH 5/7] hw/ppc: Preserve Memory Regions as per MDST/MDDT tables Aditya Gupta
2025-03-11 5:18 ` Harsh Prateek Bora
2025-03-13 18:54 ` Aditya Gupta
2025-02-17 7:19 ` [PATCH 6/7] hw/ppc: [WIP] Add Processor Dump Area offsets in Pnv SBE Aditya Gupta
2025-03-11 5:23 ` Harsh Prateek Bora
2025-03-13 18:56 ` Aditya Gupta
2025-02-17 7:19 ` [PATCH 7/7] hw/ppc: Implement MPIPL in PowerNV Aditya Gupta
2025-03-11 5:41 ` Harsh Prateek Bora
2025-03-13 19:00 ` Aditya Gupta
2025-02-27 3:37 ` [PATCH 0/7] Implement MPIPL for PowerNV Nicholas Piggin
2025-02-27 6:23 ` 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=59df1008-2127-4ae4-b8e7-72334c58f12e@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sourabhjain@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;
as well as URLs for NNTP newsgroup(s).