From: Mingzhe Yang <cainiao666999@gmail.com>
To: tglx@linutronix.de
Cc: mingo@redhat.com, bp@alien8.de, hpa@zytor.com, corbet@lwn.net,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, David.Laight@aculab.com,
Mingzhe Yang <cainiao666999@gmail.com>
Subject: [PATCH] Documentation: x86: update the thread_info's position
Date: Sat, 5 Dec 2020 13:01:36 +0800 [thread overview]
Message-ID: <1607144496-10635-1-git-send-email-cainiao666999@gmail.com> (raw)
Prior to kernel 4.9 the thread_info structure was at the bottom of
the kernel stack. kernel 4.9 moved it into the task_struct.
See commits c65eacb ("sched/core: Allow putting thread_info into
task_struct"), 15f4eae ("x86: Move thread_info into task_struct")
and 883d50f ("scripts/gdb: fix get_thread_info").
Signed-off-by: Mingzhe Yang <cainiao666999@gmail.com>
---
Documentation/x86/kernel-stacks.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/x86/kernel-stacks.rst b/Documentation/x86/kernel-stacks.rst
index 6b0bcf0..e9097f3 100644
--- a/Documentation/x86/kernel-stacks.rst
+++ b/Documentation/x86/kernel-stacks.rst
@@ -15,7 +15,8 @@ Like all other architectures, x86_64 has a kernel stack for every
active thread. These thread stacks are THREAD_SIZE (2*PAGE_SIZE) big.
These stacks contain useful data as long as a thread is alive or a
zombie. While the thread is in user space the kernel stack is empty
-except for the thread_info structure at the bottom.
+except for the thread_info structure at the bottom (since kernel 4.9,
+the thread_info structure has been moved into task_struct).
In addition to the per thread stacks, there are specialized stacks
associated with each CPU. These stacks are only used while the kernel
--
1.8.3.1
next reply other threads:[~2020-12-05 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 5:01 Mingzhe Yang [this message]
2020-12-21 16:57 ` [PATCH] Documentation: x86: update the thread_info's position Jonathan Corbet
2020-12-22 1:12 ` Mingzhe Yang
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=1607144496-10635-1-git-send-email-cainiao666999@gmail.com \
--to=cainiao666999@gmail.com \
--cc=David.Laight@aculab.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).