From: Hanjun Guo <guohanjun@huawei.com>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
James Morse <james.morse@arm.com>,
Joanthan Cameron <Jonathan.Cameron@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ACPI: PPTT: Dump PPTT table when error detected
Date: Mon, 12 Jan 2026 19:19:07 +0800 [thread overview]
Message-ID: <152465d1-08cc-898e-8ed7-9b603faaabc5@huawei.com> (raw)
In-Reply-To: <aWJqhuhuQUAKMDpF@U-2FWC9VHC-2323.local>
On 2026/1/10 23:04, Feng Tang wrote:
> Hi Hanjun,
>
[...]
>>>
>>> It provides a global and straightforward view of the hierarchy of the
>>> processor and caches info of the platform, and from the offset info
>>> (the 3rd column), the child-parent relation could be checked.
>>>
>>> With this, the root cause of the original issue was pretty obvious,
>>> that there were some caches items missing which caused the issue when
>>> building up scheduler domain.
>>
>> Just a discussion, can we just dump the raw PPTT table via acpidump
>> in user space when we meet the problem? With the raw PPTT table, we
>> can go though the content to see if we have problems.
>
> Good point! We can use iasl to decode the PPTT table. And this dump
> is still useful as:
> * when enabling new silicon or new firmware (APCI tables), sometimes it
> can't make to boot to user space when the issue happens.
> * This dump shows the processor and cache items separately and cleanly,
> while the P[]/C[] index imply the numbers. In an 128 core product ARM
> sever, the print with this patch is about 500 line, while the acpidump
> is about 10,000 lines and harder to parse.
Thanks for the user case, it makes sense to me.
>
[...]
>>> /**
>>> * topology_get_acpi_cpu_tag() - Find a unique topology value for a feature
>>> * @table: Pointer to the head of the PPTT table
>>> @@ -565,6 +638,8 @@ static int topology_get_acpi_cpu_tag(struct acpi_table_header *table,
>>> }
>>> pr_warn_once("PPTT table found, but unable to locate core %d (%d)\n",
>>> cpu, acpi_cpu_id);
>>> +
>>> + acpi_dump_pptt_table(table);
>>
>> I think it would be good to dump it as needed, as a debug feature.
>
> Makes sense to me. Should I add a kernel config option or a module
> parameter for it, or just change the pr_info to pr_debug (it's in
> a unlikely error path)?
PPTT driver can not be compiled as a module, I would like to add a
kernel config for it.
Thanks
Hanjun
next prev parent reply other threads:[~2026-01-12 11:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 10:49 Feng Tang
2026-01-10 4:29 ` Hanjun Guo
2026-01-10 15:04 ` Feng Tang
2026-01-12 11:19 ` Hanjun Guo [this message]
2026-01-12 17:02 ` Sudeep Holla
2026-01-13 8:25 ` Feng Tang
2026-01-13 14:40 ` Sudeep Holla
2026-01-14 7:06 ` Feng Tang
2026-01-14 11:36 ` Rafael J. Wysocki
2026-01-14 14:28 ` Feng Tang
2026-01-14 14:55 ` Rafael J. Wysocki
2026-01-14 15:06 ` Sudeep Holla
2026-01-14 15:07 ` Rafael J. Wysocki
2026-01-15 9:05 ` Feng Tang
2026-01-15 10:02 ` Sudeep Holla
2026-01-15 10:52 ` Feng Tang
2026-01-13 16:21 ` Rafael J. Wysocki
2026-01-14 7:47 ` Feng Tang
2026-01-14 11:41 ` Rafael J. Wysocki
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=152465d1-08cc-898e-8ed7-9b603faaabc5@huawei.com \
--to=guohanjun@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=feng.tang@linux.alibaba.com \
--cc=james.morse@arm.com \
--cc=jeremy.linton@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®