From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jiayuan Chen <mrpre@163.com>,
linux-doc@vger.kernel.org, rdunlap@infradead.org, corbet@lwn.net
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs/arch: remove deprecated function name
Date: Sat, 8 Feb 2025 11:19:47 +0700 [thread overview]
Message-ID: <Z6bbY1wsLlGvJ7Lw@archie.me> (raw)
In-Reply-To: <20250207125504.728688-1-mrpre@163.com>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
On Fri, Feb 07, 2025 at 08:55:04PM +0800, Jiayuan Chen wrote:
> The dumpstack.c file has undergone many modifications, and the
> print_context_stack() function was removed or rewritten a long time ago,
> so it's better to remove the incorrect guidance.
"print_context_stack() was removed in 2016 by commit c8fe4609827ae
("x86/dumpstack: Remove dump_trace() and related callbacks"). Remove
the now-inaccurate guide."
>
> I also want to preserve the original contributor info by keeping email
> address and name.
>
"While at it, also link to Ingo's explanatory message."
> The question about the '?' preceding function names in an x86 stacktrace
> -keeps popping up, here's an indepth explanation. It helps if the reader
> -stares at print_context_stack() and the whole machinery in and around
> -arch/x86/kernel/dumpstack.c.
> +keeps popping up. This provides guidance about it. It helps if the reader
> +stares at printk_stack_addressk() and its callers and pays special
"... Here's the explanation, that helps when the reader ..."
> +attention to the 'reliable' parameter ('?' basically means that the
> +address is unreliable).
>
> -Adapted from Ingo's mail, Message-ID: <20150521101614.GA10889@gmail.com>:
> +The detail about '?' can be found in the comments within dumpstack.c:
> +::
"The answer can be found in the comments within show_trace_log_lvl() body
in arch/x86/kernel/dumpstack.c::"
><snipped>...
> -If the address does not fit into our expected frame pointer chain we
> -still print it, but we print a '?'. It can mean two things:
> +You can also get more info from Ingo's original emal. [1]_
"For more information, see also Ingo's email. [1]_"
><snipped>...
> +.. [1] https://lore.kernel.org/lkml/20150521101614.GA10889@gmail.com/
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-02-08 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 12:55 Jiayuan Chen
2025-02-07 22:16 ` Randy Dunlap
2025-02-08 4:19 ` Bagas Sanjaya [this message]
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=Z6bbY1wsLlGvJ7Lw@archie.me \
--to=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mrpre@163.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®