All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: mario.limonciello@amd.com, robert.moore@intel.com,
	rafael.j.wysocki@intel.com, linux-acpi@vger.kernel.org,
	acpica-devel@lists.linux.dev
Subject: Re: [PATCH] Decrease `AcpiExTracePoint` verbosity
Date: Mon, 9 Jun 2025 07:48:55 -0500	[thread overview]
Message-ID: <2825b98d-1bbf-4312-899d-c0eea0854d51@kernel.org> (raw)
In-Reply-To: <CAJZ5v0iNoT79e9RRraifMY84oR8QAcSeYwk+=vaRSuB9mGmtAA@mail.gmail.com>

On 6/9/2025 4:31 AM, Rafael J. Wysocki wrote:
> On Mon, Jun 9, 2025 at 5:29 AM Mario Limonciello <superm1@kernel.org> wrote:
>>
>> From: Mario Limonciello <mario.limonciello@amd.com>
>>
>> Early in kernel boot pointers can't be used and so %p shows up
>> incorrectly:
>>
>> ```
>> extrace-0138 ex_trace_point        : Method Begin [0x(____ptrval____):\M460] execution.
>> ```
>>
>> Later in the boot %p works, but it's not really actually useful when
>> the pathname can resolve properly. Adjust the debug print so that if
>> the Pathname resolves that the pointer isn't also printed:
>>
>> ```
>> extrace-0138 ex_trace_point        : Method Begin [\M460] execution.
>> ```
>>
>> Link: https://github.com/acpica/acpica/pull/1013
>> Link: https://github.com/acpica/acpica/commit/bdc2a4e646f097b693aa60f1f2c4228d1e31b0d1
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> 
> This is an ACPICA change, so it should be made upstream first unless
> there is a good enough reason to make it directly in Linux.  In which
> case that reason should be mentioned in the changelog.

The patches were from ACPICA (I included the links above).  I wasn't 
sure if it needed to be a manual application here or if you'll do it the 
next cycle.  If you're going to automatically do it then we can 
disregard this patch for now.

> 
>> ---
>>   drivers/acpi/acpica/extrace.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/acpi/acpica/extrace.c b/drivers/acpi/acpica/extrace.c
>> index d34497f3576a4..36934d4f26fb4 100644
>> --- a/drivers/acpi/acpica/extrace.c
>> +++ b/drivers/acpi/acpica/extrace.c
>> @@ -136,9 +136,9 @@ acpi_ex_trace_point(acpi_trace_event_type type,
>>
>>          if (pathname) {
>>                  ACPI_DEBUG_PRINT((ACPI_DB_TRACE_POINT,
>> -                                 "%s %s [0x%p:%s] execution.\n",
>> +                                 "%s %s [%s] execution.\n",
>>                                    acpi_ex_get_trace_event_name(type),
>> -                                 begin ? "Begin" : "End", aml, pathname));
>> +                                 begin ? "Begin" : "End", pathname));
>>          } else {
>>                  ACPI_DEBUG_PRINT((ACPI_DB_TRACE_POINT,
>>                                    "%s %s [0x%p] execution.\n",
>> --
>> 2.43.0
>>
>>


  reply	other threads:[~2025-06-09 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09  3:28 [PATCH] Decrease `AcpiExTracePoint` verbosity Mario Limonciello
2025-06-09  9:31 ` Rafael J. Wysocki
2025-06-09 12:48   ` Mario Limonciello [this message]
2025-06-26 18:59     ` 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=2825b98d-1bbf-4312-899d-c0eea0854d51@kernel.org \
    --to=superm1@kernel.org \
    --cc=acpica-devel@lists.linux.dev \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.