From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Cc: sshegde@linux.ibm.com, npiggin@gmail.com,
christophe.leroy@csgroup.eu, maddy@linux.ibm.com,
bigeasy@linutronix.de, ankur.a.arora@oracle.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] powerpc: Enable lazy preemption
Date: Sun, 17 Nov 2024 00:53:04 +0530 [thread overview]
Message-ID: <20241116192306.88217-1-sshegde@linux.ibm.com> (raw)
preempt=lazy has been merged into tip[1]. Lets Enable it for PowerPC.
This has been very lightly tested and as michael suggested could go
through a test cycle. If needed, patches can be merged. I have kept it
separate for easier bisect.
Lazy preemption support for kvm on powerpc is still to be done.
Refs:
[1]: https://lore.kernel.org/lkml/20241007074609.447006177@infradead.org/
v1: https://lore.kernel.org/all/20241108101853.277808-1-sshegde@linux.ibm.com/
Changes since v1:
- Change for vmx copy as suggested by Sebastian.
- Add rwb tags
Shrikanth Hegde (2):
powerpc: Add preempt lazy support
powerpc: Large user copy aware of full:rt:lazy preemption
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/thread_info.h | 9 ++++++---
arch/powerpc/kernel/interrupt.c | 4 ++--
arch/powerpc/lib/vmx-helper.c | 2 +-
4 files changed, 10 insertions(+), 6 deletions(-)
--
2.43.5
next reply other threads:[~2024-11-16 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 19:23 Shrikanth Hegde [this message]
2024-11-16 19:23 ` [PATCH v2 1/2] powerpc: Add preempt lazy support Shrikanth Hegde
2024-11-26 10:53 ` Christophe Leroy
2024-12-01 19:28 ` Shrikanth Hegde
2024-12-09 7:43 ` Luming Yu
2024-11-16 19:23 ` [PATCH v2 2/2] powerpc: Large user copy aware of full:rt:lazy preemption Shrikanth Hegde
2024-11-19 21:08 ` Ankur Arora
2024-11-20 8:03 ` Sebastian Andrzej Siewior
2024-11-20 15:33 ` Shrikanth Hegde
2024-11-20 8:00 ` Sebastian Andrzej Siewior
2024-11-20 18:10 ` Shrikanth Hegde
2024-12-10 11:22 ` [PATCH v2 0/2] powerpc: Enable lazy preemption Shrikanth Hegde
2025-01-01 9:08 ` Madhavan Srinivasan
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=20241116192306.88217-1-sshegde@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=mpe@ellerman.id.au \
--cc=npiggin@gmail.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).