From: Ard Biesheuvel <ardb@kernel•org>
To: linux-kernel@vger•kernel.org
Cc: Peter Zijlstra <peterz@infradead•org>,
Paul Mackerras <paulus@samba•org>,
linux-riscv@lists•infradead.org, Will Deacon <will@kernel•org>,
Ard Biesheuvel <ardb@kernel•org>,
linux-s390@vger•kernel.org, Arnd Bergmann <arnd@arndb•de>,
Russell King <linux@armlinux•org.uk>,
Christian Borntraeger <borntraeger@de•ibm.com>,
Ingo Molnar <mingo@redhat•com>,
Catalin Marinas <catalin.marinas@arm•com>,
Albert Ou <aou@eecs•berkeley.edu>,
Kees Cook <keescook@chromium•org>,
Vasily Gorbik <gor@linux•ibm.com>,
Heiko Carstens <hca@linux•ibm.com>,
Keith Packard <keithpac@amazon•com>,
Borislav Petkov <bp@alien8•de>, Andy Lutomirski <luto@kernel•org>,
Paul Walmsley <paul.walmsley@sifive•com>,
Thomas Gleixner <tglx@linutronix•de>,
linux-arm-kernel@lists•infradead.org,
linuxppc-dev@lists•ozlabs.org,
Palmer Dabbelt <palmer@dabbelt•com>,
Linus Torvalds <torvalds@linux-foundation•org>
Subject: [RFC PATCH 3/8] s390: add CPU field to struct thread_info
Date: Tue, 14 Sep 2021 14:10:31 +0200 [thread overview]
Message-ID: <20210914121036.3975026-4-ardb@kernel.org> (raw)
In-Reply-To: <20210914121036.3975026-1-ardb@kernel.org>
The CPU field will be moved back into thread_info even when
THREAD_INFO_IN_TASK is enabled, so add it back to s390's definition of
struct thread_info.
Signed-off-by: Ard Biesheuvel <ardb@kernel•org>
---
arch/s390/include/asm/thread_info.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/s390/include/asm/thread_info.h b/arch/s390/include/asm/thread_info.h
index e6674796aa6f..b2ffcb4fe000 100644
--- a/arch/s390/include/asm/thread_info.h
+++ b/arch/s390/include/asm/thread_info.h
@@ -37,6 +37,7 @@
struct thread_info {
unsigned long flags; /* low level flags */
unsigned long syscall_work; /* SYSCALL_WORK_ flags */
+ unsigned int cpu; /* current CPU */
};
/*
--
2.30.2
next prev parent reply other threads:[~2021-09-14 12:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 12:10 [RFC PATCH 0/8] Move task_struct::cpu back into thread_info Ard Biesheuvel
2021-09-14 12:10 ` [RFC PATCH 1/8] arm64: add CPU field to struct thread_info Ard Biesheuvel
2021-09-14 15:41 ` Linus Torvalds
2021-09-14 15:42 ` Ard Biesheuvel
2021-09-16 14:41 ` Catalin Marinas
2021-09-21 12:04 ` Ard Biesheuvel
2021-09-14 12:10 ` [RFC PATCH 2/8] x86: " Ard Biesheuvel
2021-09-21 12:54 ` Borislav Petkov
2021-09-14 12:10 ` Ard Biesheuvel [this message]
2021-09-28 13:52 ` [RFC PATCH 3/8] s390: " Ard Biesheuvel
2021-09-14 12:10 ` [RFC PATCH 4/8] powerpc: " Ard Biesheuvel
2021-09-27 15:12 ` Ard Biesheuvel
2021-09-27 23:13 ` Michael Ellerman
2021-09-28 0:16 ` Michael Ellerman
2021-09-28 13:18 ` Ard Biesheuvel
2021-09-29 22:46 ` Michael Ellerman
2021-09-29 23:10 ` Kees Cook
2021-09-30 17:47 ` Kees Cook
2021-10-05 1:55 ` Michael Ellerman
2021-09-14 12:10 ` [RFC PATCH 5/8] sched: move CPU field back into thread_info if THREAD_INFO_IN_TASK=y Ard Biesheuvel
2021-09-14 15:46 ` Linus Torvalds
2021-09-14 15:52 ` Ard Biesheuvel
2021-09-14 15:58 ` Linus Torvalds
2021-09-14 16:10 ` Ard Biesheuvel
2021-09-21 13:12 ` Catalin Marinas
2021-09-14 12:10 ` [RFC PATCH 6/8] powerpc: smp: remove hack to obtain offset of task_struct::cpu Ard Biesheuvel
2021-09-14 12:10 ` [RFC PATCH 7/8] riscv: rely on core code to keep thread_info::cpu updated Ard Biesheuvel
2021-09-28 22:07 ` Palmer Dabbelt
2021-09-14 12:10 ` [RFC PATCH 8/8] ARM: " Ard Biesheuvel
2021-09-14 13:49 ` [RFC PATCH 0/8] Move task_struct::cpu back into thread_info Christophe Leroy
2021-09-14 13:55 ` Mark Rutland
2021-09-21 12:06 ` 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=20210914121036.3975026-4-ardb@kernel.org \
--to=ardb@kernel$(echo .)org \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=arnd@arndb$(echo .)de \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=bp@alien8$(echo .)de \
--cc=catalin.marinas@arm$(echo .)com \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=keescook@chromium$(echo .)org \
--cc=keithpac@amazon$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=luto@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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