mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Ard Biesheuvel <ardb@kernel.org>, linux-kernel@vger.kernel.org
Cc: Keith Packard <keithpac@amazon.com>,
	Russell King <linux@armlinux.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Heiko Carstens <hca@linux.ibm.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 5/7] sched: move CPU field back into thread_info if THREAD_INFO_IN_TASK=y
Date: Thu, 30 Sep 2021 15:08:56 +0200	[thread overview]
Message-ID: <427566ca-80c0-56eb-880b-908bd4a71e9a@csgroup.eu> (raw)
In-Reply-To: <20210930125813.197418-6-ardb@kernel.org>



Le 30/09/2021 à 14:58, Ard Biesheuvel a écrit :
> THREAD_INFO_IN_TASK moved the CPU field out of thread_info, but this
> causes some issues on architectures that define raw_smp_processor_id()
> in terms of this field, due to the fact that #include'ing linux/sched.h
> to get at struct task_struct is problematic in terms of circular
> dependencies.
> 
> Given that thread_info and task_struct are the same data structure
> anyway when THREAD_INFO_IN_TASK=y, let's move it back so that having
> access to the type definition of struct thread_info is sufficient to
> reference the CPU number of the current task.
> 
> Note that this requires THREAD_INFO_IN_TASK's definition of the
> task_thread_info() helper to be updated, as task_cpu() takes a
> pointer-to-const, whereas task_thread_info() (which is used to generate
> lvalues as well), needs a non-const pointer. So make it a macro instead.
> 
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> Acked-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
>   arch/arm64/kernel/asm-offsets.c   |  1 -
>   arch/arm64/kernel/head.S          |  2 +-
>   arch/powerpc/kernel/asm-offsets.c |  2 +-
>   arch/powerpc/kernel/smp.c         |  2 +-
>   include/linux/sched.h             | 13 +------------
>   kernel/sched/sched.h              |  4 ----
>   6 files changed, 4 insertions(+), 20 deletions(-)
> 
> diff --git a/arch/arm64/kernel/asm-offsets.c b/arch/arm64/kernel/asm-offsets.c
> index cee9f3e9f906..0bfc048221af 100644
> --- a/arch/arm64/kernel/asm-offsets.c
> +++ b/arch/arm64/kernel/asm-offsets.c
> @@ -27,7 +27,6 @@
>   int main(void)
>   {
>     DEFINE(TSK_ACTIVE_MM,		offsetof(struct task_struct, active_mm));
> -  DEFINE(TSK_CPU,		offsetof(struct task_struct, cpu));
>     BLANK();
>     DEFINE(TSK_TI_CPU,		offsetof(struct task_struct, thread_info.cpu));
>     DEFINE(TSK_TI_FLAGS,		offsetof(struct task_struct, thread_info.flags));
> diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
> index 17962452e31d..6a98f1a38c29 100644
> --- a/arch/arm64/kernel/head.S
> +++ b/arch/arm64/kernel/head.S
> @@ -412,7 +412,7 @@ SYM_FUNC_END(__create_page_tables)
>   	scs_load \tsk
>   
>   	adr_l	\tmp1, __per_cpu_offset
> -	ldr	w\tmp2, [\tsk, #TSK_CPU]
> +	ldr	w\tmp2, [\tsk, #TSK_TI_CPU]

Why do you need to change the name ?

For powerpc64, you leave TASK_CPU.

>   	ldr	\tmp1, [\tmp1, \tmp2, lsl #3]
>   	set_this_cpu_offset \tmp1
>   	.endm
> diff --git a/arch/powerpc/kernel/asm-offsets.c b/arch/powerpc/kernel/asm-offsets.c
> index e563d3222d69..e37e4546034e 100644
> --- a/arch/powerpc/kernel/asm-offsets.c
> +++ b/arch/powerpc/kernel/asm-offsets.c
> @@ -93,7 +93,7 @@ int main(void)
>   #endif /* CONFIG_PPC64 */
>   	OFFSET(TASK_STACK, task_struct, stack);
>   #ifdef CONFIG_SMP
> -	OFFSET(TASK_CPU, task_struct, cpu);
> +	OFFSET(TASK_CPU, task_struct, thread_info.cpu);
>   #endif
>   
>   #ifdef CONFIG_LIVEPATCH

...

  reply	other threads:[~2021-09-30 13:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 12:58 [PATCH v2 0/7] Move task_struct::cpu back into thread_info Ard Biesheuvel
2021-09-30 12:58 ` [PATCH v2 1/7] arm64: add CPU field to struct thread_info Ard Biesheuvel
2021-09-30 13:06   ` Christophe Leroy
2021-09-30 13:07     ` Ard Biesheuvel
2021-09-30 13:15       ` Christophe Leroy
2021-09-30 13:20         ` Ard Biesheuvel
2021-09-30 13:23           ` Christophe Leroy
2021-09-30 12:58 ` [PATCH v2 2/7] x86: " Ard Biesheuvel
2021-09-30 12:58 ` [PATCH v2 3/7] s390: " Ard Biesheuvel
2021-09-30 13:02   ` Heiko Carstens
2021-09-30 12:58 ` [PATCH v2 4/7] powerpc: " Ard Biesheuvel
2021-09-30 12:58 ` [PATCH v2 5/7] sched: move CPU field back into thread_info if THREAD_INFO_IN_TASK=y Ard Biesheuvel
2021-09-30 13:08   ` Christophe Leroy [this message]
2021-09-30 13:12     ` Ard Biesheuvel
2021-09-30 13:22       ` Christophe Leroy
2021-09-30 13:35         ` Christophe Leroy
2021-09-30 12:58 ` [PATCH v2 6/7] powerpc: smp: remove hack to obtain offset of task_struct::cpu Ard Biesheuvel
2021-09-30 12:58 ` [PATCH v2 7/7] riscv: rely on core code to keep thread_info::cpu updated Ard Biesheuvel

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=427566ca-80c0-56eb-880b-908bd4a71e9a@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=catalin.marinas@arm.com \
    --cc=hca@linux.ibm.com \
    --cc=keithpac@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mpe@ellerman.id.au \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulus@samba.org \
    --cc=will@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®