From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: Shyam-sundar.S-k@amd.com, Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/amd/pmc: Add AMD MP2 STB functionality
Date: Tue, 27 Feb 2024 12:48:19 +0200 (EET) [thread overview]
Message-ID: <2294f1e9-2da3-aa07-dac1-02ffc402a424@linux.intel.com> (raw)
In-Reply-To: <20240226151309.2147799-1-Basavaraj.Natikar@amd.com>
On Mon, 26 Feb 2024, Basavaraj Natikar wrote:
> AMD MP2 STB function provides a data buffer used to log debug information
> about the system execution during S2Idle suspend/resume.
>
> A data buffer known as the STB (Smart Trace Buffer) is a circular buffer
> which is a low-level log to assist in debugging by providing insights
> into any potential hangs or stalls that may occur during the S2Idle
> suspend/resume processes.
>
> The current PMC driver retrieves STB data from MP1, but there can be
> scenarios where MP1 might hang or become unresponsive, leading to the
> loss of critical data present in the STB buffer. This defeats the purpose
> of the STB buffer, which was originally meant to help identify system
> failures.
>
> This feature creates stb_read_previous_boot debugfs allows users to
> retrieve the STB log from MP2 specifically from the last occurrence of
> the S2Idle suspend/resume. A userspace daemon can access STB log of last
> S2Idle suspend/resume which can help to troubleshoot potential issues
> related to hangs or stalls during the S2Idle suspend/resume sequence.
>
> Reviewed-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
> ---
> Changes in v2:
> - Used linux/sizes.h instead of defining KB.
> - Defined timeout containing unit as per USEC_PER_MSEC.
> - Modified macro of AMD_C2P_MSG and AMD_P2C_MSG.
> - Changed string stb to STB in log messages.
> - Defined literals using Macro.
>
> drivers/platform/x86/amd/pmc/Kconfig | 23 +++
> drivers/platform/x86/amd/pmc/Makefile | 1 +
> drivers/platform/x86/amd/pmc/mp2_stb.c | 227 +++++++++++++++++++++++++
> drivers/platform/x86/amd/pmc/pmc.c | 5 +
> drivers/platform/x86/amd/pmc/pmc.h | 12 ++
> 5 files changed, 268 insertions(+)
> create mode 100644 drivers/platform/x86/amd/pmc/mp2_stb.c
>
> diff --git a/drivers/platform/x86/amd/pmc/Kconfig b/drivers/platform/x86/amd/pmc/Kconfig
> index 883c0a95ac0c..8177486babf9 100644
> --- a/drivers/platform/x86/amd/pmc/Kconfig
> +++ b/drivers/platform/x86/amd/pmc/Kconfig
> @@ -18,3 +18,26 @@ config AMD_PMC
>
> If you choose to compile this driver as a module the module will be
> called amd-pmc.
> +
> +config AMD_MP2_STB
> + bool "AMD SoC MP2 STB function"
> + depends on AMD_PMC
> + help
> + AMD MP2 STB function provides a data buffer used to log debug
> + information about the system execution during S2Idle suspend/resume.
> + A data buffer known as the STB (Smart Trace Buffer) is a circular
> + buffer which is a low-level log for the SoC which is used to debug
> + any hangs/stalls during S2Idle suspend/resume.
> +
> + The current PMC driver retrieves STB data from MP1, but there can be
> + scenarios where MP1 might hang or become unresponsive, leading to the
> + loss of critical data present in the STB buffer. This defeats the
> + purpose of the STB buffer, which was originally meant to help identify
> + system failures.
> +
> + Creates stb_read_previous_boot debugfs to get STB, a userspace daemon
> + can access STB log of last S2Idle suspend/resume which can help to
> + debug if hangs/stalls during S2Idle suspend/resume
> +
> + Say Y or N here if you have a notebook powered by AMD RYZEN CPU/APU
> + and supports MP2 STB.
> diff --git a/drivers/platform/x86/amd/pmc/Makefile b/drivers/platform/x86/amd/pmc/Makefile
> index 4aaa29d351c9..f1d9ab19d24c 100644
> --- a/drivers/platform/x86/amd/pmc/Makefile
> +++ b/drivers/platform/x86/amd/pmc/Makefile
> @@ -6,3 +6,4 @@
>
> amd-pmc-objs := pmc.o pmc-quirks.o
> obj-$(CONFIG_AMD_PMC) += amd-pmc.o
> +amd-pmc-$(CONFIG_AMD_MP2_STB) += mp2_stb.o
> diff --git a/drivers/platform/x86/amd/pmc/mp2_stb.c b/drivers/platform/x86/amd/pmc/mp2_stb.c
> new file mode 100644
> index 000000000000..258de76cddce
> --- /dev/null
> +++ b/drivers/platform/x86/amd/pmc/mp2_stb.c
> @@ -0,0 +1,227 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * AMD MP2 STB layer
> + *
> + * Copyright (c) 2024, Advanced Micro Devices, Inc.
> + * All Rights Reserved.
> + *
> + * Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
> + */
> +
> +#include <linux/debugfs.h>
> +#include <linux/iopoll.h>
> +#include <linux/pci.h>
> +#include <linux/sizes.h>
> +
> +#include "pmc.h"
> +
> +#define VALID_MSG 0xA
> +#define VALID_RESPONSE 2
> +
> +#define AMD_C2P_MSG0 0x10500
> +#define AMD_C2P_MSG1 0x10504
> +#define AMD_P2C_MSG0 0x10680
> +#define AMD_P2C_MSG1 0x10684
> +
> +#define SLEEP_US (0.5 * USEC_PER_MSEC)
Thanks for the update.
This needs to be just 500.
> +#define TIMEOUT_US (1600 * USEC_PER_MSEC)
Please be more specific in naming what these are. Perhaps
MP2_RESP_TIMEOUT_US & MP2_RESP_SLEEP_US ?
Add #include <linux/time.h> for USEC_PER_MSEC
> +#define LEN_2KB_BIT 1
> +#define LEN_16KB_BIT 4
These are way too generic names. I expected something like:
#define MP2_STB_DATA_LEN_2KB ...
> +
> +static struct amd_mp2_dev *mp2;
> +
> +struct mp2_cmd_base {
> + union {
> + u32 ul;
> + struct {
> + u32 cmd_id : 4;
> + u32 intr_disable : 1;
> + u32 dma_addr : 1;
> + u32 rsvd : 26;
> + } cmd;
> + };
> +};
> +
> +struct mp2_cmd_response {
> + union {
> + u32 resp;
> + struct {
> + u32 cmd_id : 4;
> + u32 status : 4;
> + u32 response : 4;
> + u32 rsvd2 : 20;
> + } response;
> + };
> +};
> +
> +struct mp2_stb_data_valid {
> + union {
> + u32 data_valid;
> + struct {
> + u32 valid : 16;
> + u32 length : 16;
> + } val;
> + };
> +};
> +
> +static int amd_mp2_wait_response(u8 cmd_id, u32 command_sts)
> +{
> + struct mp2_cmd_response cmd_resp;
> +
> + if (!readl_poll_timeout(mp2->mmio + AMD_P2C_MSG0, cmd_resp.resp,
> + (cmd_resp.response.response == 0x0 &&
> + cmd_resp.response.status == command_sts &&
> + cmd_resp.response.cmd_id == cmd_id), SLEEP_US, TIMEOUT_US))
> + return cmd_resp.response.status;
> +
> + return -ETIMEDOUT;
> +}
> +
> +static void amd_mp2_stb_send_cmd(u8 cmd_id, uint8_t da)
So 'da' is assigned to .dma_addr, why is the parameter only obfuscatingly
as 'da' ?
> +{
> + struct mp2_cmd_base cmd_base;
> +
> + cmd_base.ul = 0;
> + cmd_base.cmd.cmd_id = cmd_id;
> + cmd_base.cmd.intr_disable = 1;
> + cmd_base.cmd.dma_addr = da;
> +
> + writeq(mp2->dma_addr, mp2->mmio + AMD_C2P_MSG1);
> + writel(cmd_base.ul, mp2->mmio + AMD_C2P_MSG0);
Please add the #include for writeq() and writel() like I already told you.
> +}
> +
> +static int amd_mp2_stb_region(int len)
size_t or unsigned int?
> +{
> + struct device *dev = &mp2->pdev->dev;
> +
> + len *= SZ_1K;
> +
> + if (!mp2->stbdata) {
> + mp2->vslbase = dmam_alloc_coherent(dev, len, &mp2->dma_addr, GFP_KERNEL);
> + if (!mp2->vslbase)
> + return -ENOMEM;
> +
> + mp2->stbdata = devm_kzalloc(dev, len, GFP_KERNEL);
> + if (!mp2->stbdata)
> + return -ENOMEM;
> + }
> +
> + return 0;
> +}
> +
> +static int amd_mp2_process_cmd(struct file *filp)
> +{
> + struct mp2_stb_data_valid stb_dv;
> + int status, rc;
> +
> + stb_dv.data_valid = readl(mp2->mmio + AMD_P2C_MSG1);
> +
> + if (stb_dv.val.valid != VALID_MSG) {
> + dev_err(&mp2->pdev->dev, "Invalid STB data\n");
> + return -EBADMSG;
> + }
> +
> + if (stb_dv.val.length != LEN_2KB_BIT && stb_dv.val.length != LEN_16KB_BIT) {
> + dev_err(&mp2->pdev->dev, "Unsupported length\n");
> + return -EMSGSIZE;
> + }
> +
> + mp2->stb_len = BIT(stb_dv.val.length);
> +
> + rc = amd_mp2_stb_region(mp2->stb_len);
> + if (rc) {
> + dev_err(&mp2->pdev->dev, "Failed to init STB region, rc %d\n", rc);
> + return rc;
> + }
> +
> + amd_mp2_stb_send_cmd(VALID_MSG, true);
> + status = amd_mp2_wait_response(VALID_MSG, VALID_RESPONSE);
> + if (status == VALID_RESPONSE) {
I'd just use single variable for return values, after all, status and rc
are both ints.
> + memcpy_fromio(mp2->stbdata, mp2->vslbase, SZ_1K * mp2->stb_len);
> + filp->private_data = mp2->stbdata;
> + mp2->is_stb_data = true;
> + } else {
> + dev_err(&mp2->pdev->dev, "Failed to start STB dump, status %d\n", status);
> + return -EOPNOTSUPP;
> + }
> +
> + return 0;
> +}
--
i.
next prev parent reply other threads:[~2024-02-27 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 15:13 [PATCH v2] platform/x86/amd/pmc: Add AMD MP2 STB functionality Basavaraj Natikar
2024-02-26 18:18 ` Kuppuswamy Sathyanarayanan
2024-02-28 10:46 ` Basavaraj Natikar
2024-02-27 10:48 ` Ilpo Järvinen [this message]
2024-02-28 10:48 ` Basavaraj Natikar
2024-02-29 11:25 ` Ilpo Järvinen
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=2294f1e9-2da3-aa07-dac1-02ffc402a424@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=platform-driver-x86@vger.kernel.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