From: David Disseldorp <ddiss@suse.de>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel-library@freelists.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Mel Gorman <mgorman@suse.de>, Hajime Tazaki <thehajime@gmail.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] sched: remove unused __HAVE_THREAD_FUNCTIONS hook support
Date: Fri, 30 Aug 2024 01:25:35 +0000 [thread overview]
Message-ID: <20240830012535.6b6f6de1.ddiss@suse.de> (raw)
In-Reply-To: <20240822043328.4180-1-ddiss@suse.de>
[cc'ing Ard as ia64 remover]
Ping - any thoughts on this patch?
On Thu, 22 Aug 2024 04:33:28 +0000, David Disseldorp wrote:
> __HAVE_THREAD_FUNCTIONS could be defined by architectures wishing to
> provide their own task_thread_info(), task_stack_page(),
> setup_thread_stack() and end_of_stack() hooks.
>
> Commit cf8e8658100d ("arch: Remove Itanium (IA-64) architecture")
> removed the last upstream consumer of __HAVE_THREAD_FUNCTIONS, so change
> the remaining !CONFIG_THREAD_INFO_IN_TASK && !__HAVE_THREAD_FUNCTIONS
> conditionals to only check for the former case.
>
> Signed-off-by: David Disseldorp <ddiss@suse.de>
> ---
> include/linux/sched.h | 2 +-
> include/linux/sched/task_stack.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index f8d150343d42..9dbcdfe173cf 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1874,7 +1874,7 @@ extern unsigned long init_stack[THREAD_SIZE / sizeof(unsigned long)];
>
> #ifdef CONFIG_THREAD_INFO_IN_TASK
> # define task_thread_info(task) (&(task)->thread_info)
> -#elif !defined(__HAVE_THREAD_FUNCTIONS)
> +#else
> # define task_thread_info(task) ((struct thread_info *)(task)->stack)
> #endif
>
> diff --git a/include/linux/sched/task_stack.h b/include/linux/sched/task_stack.h
> index ccd72b978e1f..55042ff01a6d 100644
> --- a/include/linux/sched/task_stack.h
> +++ b/include/linux/sched/task_stack.h
> @@ -33,7 +33,7 @@ static __always_inline unsigned long *end_of_stack(const struct task_struct *tas
> #endif
> }
>
> -#elif !defined(__HAVE_THREAD_FUNCTIONS)
> +#else
>
> #define task_stack_page(task) ((void *)(task)->stack)
>
next prev parent reply other threads:[~2024-08-30 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 4:33 David Disseldorp
2024-08-30 1:25 ` David Disseldorp [this message]
2024-08-30 9:07 ` 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=20240830012535.6b6f6de1.ddiss@suse.de \
--to=ddiss@suse.de \
--cc=ardb@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel-library@freelists.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thehajime@gmail.com \
--cc=vincent.guittot@linaro.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®