From: Ingo Molnar <mingo@kernel.org>
To: "Xin Li (Intel)" <xin@zytor.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-arch@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, jgross@suse.com, boris.ostrovsky@oracle.com,
arnd@arndb.de, Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH v2 1/1] x86: Rename __{start,end}_init_task to __{start,end}_init_stack
Date: Thu, 21 Mar 2024 20:54:37 +0100 [thread overview]
Message-ID: <ZfyQfQrluph6GxLS@gmail.com> (raw)
In-Reply-To: <20240318071429.910454-1-xin@zytor.com>
* Xin Li (Intel) <xin@zytor.com> wrote:
> The stack of a task has been separated from the memory of a task_struct
> struture for a long time on x86, as a result __{start,end}_init_task no
> longer mark the start and end of the init_task structure, but its stack
> only.
>
> Rename __{start,end}_init_task to __{start,end}_init_stack.
>
> Note other architectures are not affected because __{start,end}_init_task
> are used on x86 only.
>
> Signed-off-by: Xin Li (Intel) <xin@zytor.com>
> ---
>
> Change since v1:
> * Revert an accident insane change, init_task to init_stack (Jürgen Groß).
> ---
> arch/x86/include/asm/processor.h | 4 ++--
> arch/x86/kernel/head_64.S | 2 +-
> arch/x86/xen/xen-head.S | 2 +-
> include/asm-generic/vmlinux.lds.h | 6 +++---
> 4 files changed, 7 insertions(+), 7 deletions(-)
Note that this is now in conflict with this cleanup by Brian Gerst:
2cb16181a1d1 x86/boot: Simplify boot stack setup
... which removed __end_init_task[] entirely.
Thanks,
Ingo
next prev parent reply other threads:[~2024-03-21 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 7:14 [PATCH v2 1/1] x86: Rename __{start,end}_init_task to __{start,end}_init_stack Xin Li (Intel)
2024-03-18 7:23 ` Jürgen Groß
2024-03-21 19:54 ` Ingo Molnar [this message]
2024-03-22 4:59 ` Xin Li
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=ZfyQfQrluph6GxLS@gmail.com \
--to=mingo@kernel.org \
--cc=arnd@arndb.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xin@zytor.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;
as well as URLs for NNTP newsgroup(s).