From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
mpe@ellerman.id.au, 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
Subject: Re: [PATCH 2/3] powerpc: support dynamic preemption
Date: Mon, 2 Dec 2024 01:15:41 +0530 [thread overview]
Message-ID: <ff4c586b-7be7-4c31-8b8c-5846ded486de@linux.ibm.com> (raw)
In-Reply-To: <5089fd16-bc8c-4231-a89b-2658445e04b7@csgroup.eu>
On 11/27/24 12:14, Christophe Leroy wrote:
>
>
> Le 25/11/2024 à 05:22, Shrikanth Hegde a écrit :
>> Once the lazy preemption is supported, it would be desirable to change
>> the preemption models at runtime. So this change adds support for dynamic
>> preemption using DYNAMIC_KEY.
>>
>> In irq-exit to kernel path, use preempt_model_preemptible for decision.
>> Other way would be using static key based decision. Keeping it
>> simpler since key based change didn't show performance improvement.
>
> What about static_call, wouldn't it improve performance ?
>
>>
>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
>> index 6d6bbd93abab..01c58f5258c9 100644
>> --- a/arch/powerpc/Kconfig
>> +++ b/arch/powerpc/Kconfig
>> @@ -270,6 +270,7 @@ config PPC
>> select HAVE_PERF_EVENTS_NMI if PPC64
>> select HAVE_PERF_REGS
>> select HAVE_PERF_USER_STACK_DUMP
>> + select HAVE_PREEMPT_DYNAMIC_KEY
>
> Can you use HAVE_PREEPT_DYNAMIC_CALL instead ? That should be more
> performant.
>
> I know static calls are not in for PPC64 yet, you can restart from
> http://patchwork.ozlabs.org/project/linuxppc-dev/
> cover/20221010002957.128276-1-bgray@linux.ibm.com/ and https://
> github.com/linuxppc/issues/issues/416
>
Thanks Christophe, I will take a look and understand.
May be stupid question, do the concerns of arm still valid for ppc64/ppc32 out-line static calls?
https://lore.kernel.org/all/20220214165216.2231574-6-mark.rutland@arm.com/
As I understood, that is the reason they went ahead with DYNAMIC_KEY.
> Christophe
next prev parent reply other threads:[~2024-12-01 19:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 4:22 [PATCH 0/3] powerpc: Enable " 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
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 [this message]
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=ff4c586b-7be7-4c31-8b8c-5846ded486de@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=ankur.a.arora@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=christophe.leroy@csgroup.eu \
--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=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
all inboxes | Powered by JetHome®