mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@linux.alibaba.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "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>,
	Joanthan Cameron <Jonathan.Cameron@huawei.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ACPI: PPTT: Dump PPTT table when error detected
Date: Wed, 14 Jan 2026 15:06:49 +0800	[thread overview]
Message-ID: <aWdAiaC10ear9ajR@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <aWZZeD496CPi20Gc@bogus>

Hi Sudeep,

On Tue, Jan 13, 2026 at 02:40:56PM +0000, Sudeep Holla wrote:
[...]
> > > > 
> > > > 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.
> > > > 
> > > 
> > > While this may sound like a good idea, it deviates from how errors in other
> > > table-parsing code are handled. Instead of dumping the entire table, it would
> > > be preferable to report the specific issue encountered during parsing.
> > > 
> > > I do not have a strong objection if Rafael is comfortable with this approach;
> > > however, it does differ from the established pattern used by similar code.
> > > Dumping the entire table in a custom manner is not the standard way of
> > > handling parsing errors. Just my opinion.
> > 
> > Yes, it's a fair point about the error handling. Actually for the issue
> > we met, the PPTT table complies with ACPI spec and PPTT table spec nicely,
> > that it has no checksum or format issue, the only problem is some items
> > are missing. 
> > 
> 
> Agreed, but how is this any different from other tables that contain optional
> entries the ASL compiler cannot detect?
> 
> > So I would say the dump itself doesn't break any existing ACPI table error
> > handling, or change anything. As Hanjun suggested, it could be put under a
> > CONFIG_ACPI_PPTT_ERR_DUMP option as a PPTT specific debug method, and not
> > related to general ACPI table error handling.
> > 
> 
> Sure, that could be an option as long as CONFIG_ACPI_PPTT_ERR_DUMP is default
> off and are enabled only when debugging and not always like in distro images.
> Does that work for you ?

Yes. It sounds great to me.

> > We have had this in our tree for a while, and the good part is it gives a
> > direct overview of all the processors and caches in system, you get to
> > know the rough number of them from the index, and items are listed side
> > by side so that some minor error could be very obvious in this comparing
> > mode.
> > 
> 
> Agreed, but all this info are available to userspace in some form already.
> What does this dump give other than debugging a broken PPTT ?

It is mainly for debugging issues. Though we locally has option to dump it
on boot unconditionally to help kernel/BIOS devleoper to have a quick
overview of the PPTT table, as the table gets updated from time to time,
or sometime the kernel could fail before booting to user space.

Thanks,
Feng

> -- 
> Regards,
> Sudeep

  reply	other threads:[~2026-01-14  7:06 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
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 [this message]
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=aWdAiaC10ear9ajR@U-2FWC9VHC-2323.local \
    --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®