From: Feng Tang <feng.tang@linux.alibaba.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Hanjun Guo <guohanjun@huawei.com>,
James Morse <james.morse@arm.com>
Cc: Joanthan Cameron <Jonathan.Cameron@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Feng Tang <feng.tang@linux.alibaba.com>
Subject: [PATCH v2] ACPI: PPTT: Dump PPTT table when error detected
Date: Wed, 31 Dec 2025 18:49:09 +0800 [thread overview]
Message-ID: <20251231104909.80362-1-feng.tang@linux.alibaba.com> (raw)
There was warning message about PPTT table:
"ACPI PPTT: PPTT table found, but unable to locate core 1 (1)",
and it in turn caused scheduler warnings when building up the system.
It took a while to root cause the problem be related a broken PPTT
table which has wrong cache information.
To speedup debugging similar issues, dump the PPTT table, which makes
the warning more noticeable and helps bug hunting.
The dumped info format on a ARM server is like:
ACPI PPTT: Processors:
P[ 0][0x0024]: parent=0x0000 acpi_proc_id= 0 num_res=1 flags=0x11(package)
P[ 1][0x005a]: parent=0x0024 acpi_proc_id= 0 num_res=1 flags=0x12()
P[ 2][0x008a]: parent=0x005a acpi_proc_id= 0 num_res=3 flags=0x1a(leaf)
P[ 3][0x00f2]: parent=0x005a acpi_proc_id= 1 num_res=3 flags=0x1a(leaf)
P[ 4][0x015a]: parent=0x005a acpi_proc_id= 2 num_res=3 flags=0x1a(leaf)
...
ACPI PPTT: Caches:
C[ 0][0x0072]: flags=0x7f next_level=0x0000 size=0x4000000 sets=65536 way=16 attribute=0xa line_size=64
C[ 1][0x00aa]: flags=0x7f next_level=0x00da size=0x10000 sets=256 way=4 attribute=0x4 line_size=64
C[ 2][0x00c2]: flags=0x7f next_level=0x00da size=0x10000 sets=256 way=4 attribute=0x2 line_size=64
C[ 3][0x00da]: flags=0x7f next_level=0x0000 size=0x100000 sets=2048 way=8 attribute=0xa line_size=64
...
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.
Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>
---
Changelog:
v2
* rebase againt 6.19 and refine the commit log
drivers/acpi/pptt.c | 75 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 75 insertions(+)
diff --git a/drivers/acpi/pptt.c b/drivers/acpi/pptt.c
index de5f8c018333..e00abedcd786 100644
--- a/drivers/acpi/pptt.c
+++ b/drivers/acpi/pptt.c
@@ -529,6 +529,79 @@ static void acpi_pptt_warn_missing(void)
pr_warn_once("No PPTT table found, CPU and cache topology may be inaccurate\n");
}
+static void acpi_dump_pptt_table(struct acpi_table_header *table_hdr)
+{
+ struct acpi_subtable_header *entry, *entry_start;
+ unsigned long end;
+ struct acpi_pptt_processor *cpu;
+ struct acpi_pptt_cache *cache;
+ u32 entry_sz, i;
+ u8 len;
+ static bool dumped;
+
+ /* PPTT table could be pretty big, no need to dump it twice */
+ if (dumped)
+ return;
+ dumped = true;
+
+ end = (unsigned long)table_hdr + table_hdr->length;
+ entry_start = ACPI_ADD_PTR(struct acpi_subtable_header, table_hdr,
+ sizeof(struct acpi_table_pptt));
+
+ pr_info("Processors:\n");
+ entry_sz = sizeof(struct acpi_pptt_processor);
+ entry = entry_start;
+ i = 0;
+ while ((unsigned long)entry + entry_sz <= end) {
+ len = entry->length;
+ if (!len) {
+ pr_warn("Invalid zero length subtable\n");
+ return;
+ }
+
+ cpu = (struct acpi_pptt_processor *)entry;
+ entry = ACPI_ADD_PTR(struct acpi_subtable_header, entry, len);
+
+ if (cpu->header.type != ACPI_PPTT_TYPE_PROCESSOR)
+ continue;
+
+ printk(KERN_INFO "P[%3d][0x%04lx]: parent=0x%04x acpi_proc_id=%3d num_res=%d flags=0x%02x(%s%s%s)\n",
+ i++, (unsigned long)cpu - (unsigned long)table_hdr,
+ cpu->parent, cpu->acpi_processor_id,
+ cpu->number_of_priv_resources, cpu->flags,
+ cpu->flags & ACPI_PPTT_PHYSICAL_PACKAGE ? "package" : "",
+ cpu->flags & ACPI_PPTT_ACPI_LEAF_NODE ? "leaf" : "",
+ cpu->flags & ACPI_PPTT_ACPI_PROCESSOR_IS_THREAD ? ", thread" : ""
+ );
+
+ }
+
+ pr_info("Caches:\n");
+ entry_sz = sizeof(struct acpi_pptt_cache);
+ entry = entry_start;
+ i = 0;
+ while ((unsigned long)entry + entry_sz <= end) {
+ len = entry->length;
+ if (!len) {
+ pr_warn("Invalid zero length subtable\n");
+ return;
+ }
+
+ cache = (struct acpi_pptt_cache *)entry;
+ entry = ACPI_ADD_PTR(struct acpi_subtable_header, entry, len);
+
+ if (cache->header.type != ACPI_PPTT_TYPE_CACHE)
+ continue;
+
+ printk(KERN_INFO "C[%4d][0x%04lx]: flags=0x%02x next_level=0x%04x size=0x%-8x sets=%-6d way=%-2d attribute=0x%-2x line_size=%d\n",
+ i++, (unsigned long)cache - (unsigned long)table_hdr,
+ cache->flags, cache->next_level_of_cache, cache->size,
+ cache->number_of_sets, cache->associativity,
+ cache->attributes, cache->line_size
+ );
+ }
+}
+
/**
* 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);
return -ENOENT;
}
base-commit: c8ebd433459bcbf068682b09544e830acd7ed222
--
2.39.5 (Apple Git-154)
next reply other threads:[~2025-12-31 10:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 10:49 Feng Tang [this message]
2026-01-10 4:29 ` Hanjun Guo
2026-01-10 15:04 ` Feng Tang
2026-01-12 11:19 ` Hanjun Guo
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=20251231104909.80362-1-feng.tang@linux.alibaba.com \
--to=feng.tang@linux.alibaba.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=guohanjun@huawei.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®