From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Shrikanth Hegde <sshegde@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com, maddy@linux.ibm.com, bigeasy@linutronix.de,
ankur.a.arora@oracle.com, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, vschneid@redhat.com, peterz@infradead.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 1/3] powerpc: copy preempt.h into arch/include/asm
Date: Mon, 2 Dec 2024 19:17:36 +0100 [thread overview]
Message-ID: <3de6bf25-fb3c-49a9-b06b-5e2e527ec90c@csgroup.eu> (raw)
In-Reply-To: <026ad776-a889-4213-8e0e-1da9065dc5ef@linux.ibm.com>
Le 02/12/2024 à 15:05, Shrikanth Hegde a écrit :
>
>
> On 11/27/24 12:07, Christophe Leroy wrote:
>>
>>
>> Le 25/11/2024 à 05:22, Shrikanth Hegde a écrit :
>>> PowerPC uses asm-generic preempt definitions as of now.
>>> Copy that into arch/asm so that arch specific changes can be done.
>>> This would help the next patch for enabling dynamic preemption.
>>
>
> The reason I want the content instead was to allow future patches where
> I thought of making preempt count per paca for ppc64 atleast. generic
> code assumes it is per thread. If this change is to be done at that
> point, that is fair too. I am okay with it.
I think it is better to keep series minimal and consistent. If you have
a futur plan, no problem, keep it future and do everything at once
unless it is heavy and better done in two steps.
As we say in French, a lot of water will have flowed under the bridge by
then.
I'm sure there will be a lot of discussion when you do that and maybe at
the end you will end up with something completely different than what
you have in mind at the moment.
>
>
>> Instead of copying all the content of asm-generic version, can you
>> just create a receptacle for your new macros, that will include asm-
>> generic/ preempt.h ?
>>
>> Look at arch/powerpc/include/asm/percpu.h for exemple.
>>
>
> You mean something like below right?
>
>
> #ifndef __ASM_POWERPC_PREEMPT_H
> #define __ASM_POWERPC_PREEMPT_H
>
> #include <asm-generic/preempt.h>
>
> #if defined(CONFIG_PREEMPT_DYNAMIC) &&
> defined(CONFIG_HAVE_PREEMPT_DYNAMIC_KEY)
> DECLARE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
> #endif
>
> #endif /* __ASM_POWERPC_PREEMPT_H */
Yes exactly.
next prev parent reply other threads:[~2024-12-02 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 4:22 [PATCH 0/3] powerpc: Enable dynamic preemption Shrikanth Hegde
2024-11-25 4:22 ` [PATCH 1/3] powerpc: copy preempt.h into arch/include/asm Shrikanth Hegde
2024-11-26 10:49 ` Christophe Leroy
2024-11-27 6:37 ` Christophe Leroy
2024-12-02 14:05 ` Shrikanth Hegde
2024-12-02 18:17 ` Christophe Leroy [this message]
2024-12-03 14:00 ` Shrikanth Hegde
2024-12-03 19:47 ` Christophe Leroy
2024-11-25 4:22 ` [PATCH 2/3] powerpc: support dynamic preemption Shrikanth Hegde
2024-11-26 10:48 ` Christophe Leroy
2024-11-26 11:15 ` Shrikanth Hegde
2024-11-27 6:28 ` Christophe Leroy
2024-11-27 6:44 ` Christophe Leroy
2024-12-01 19:45 ` Shrikanth Hegde
2024-12-03 19:53 ` Christophe Leroy
2024-11-25 4:22 ` [PATCH 3/3] powerpc: print right preemption model in die Shrikanth Hegde
2024-12-04 6:44 ` Christophe Leroy
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=3de6bf25-fb3c-49a9-b06b-5e2e527ec90c@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=ankur.a.arora@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=vschneid@redhat.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).