From: Joachim Wiberg <troglobit@gmail•com>
To: linuxppc-dev@lists•ozlabs.org, Scott Wood <oss@buserror•net>,
Michael Ellerman <mpe@ellerman•id.au>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>
Cc: Joachim Wiberg <troglobit@gmail•com>,
Tobias Waldekranz <tobias@waldekranz•com>
Subject: [PATCH 1/1] powerpc/e500/qemu-e500: allow core to idle without waiting
Date: Wed, 12 Jan 2022 12:24:59 +0100 [thread overview]
Message-ID: <20220112112459.1033754-1-troglobit@gmail.com> (raw)
From: Tobias Waldekranz <tobias@waldekranz•com>
This means an idle guest won't needlessly consume an entire core on
the host, waiting for work to show up.
Signed-off-by: Tobias Waldekranz <tobias@waldekranz•com>
Signed-off-by: Joachim Wiberg <troglobit@gmail•com>
---
arch/powerpc/platforms/85xx/qemu_e500.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/platforms/85xx/qemu_e500.c b/arch/powerpc/platforms/85xx/qemu_e500.c
index a4127b0b161f..4c4d577effd9 100644
--- a/arch/powerpc/platforms/85xx/qemu_e500.c
+++ b/arch/powerpc/platforms/85xx/qemu_e500.c
@@ -67,4 +67,9 @@ define_machine(qemu_e500) {
.get_irq = mpic_get_coreint_irq,
.calibrate_decr = generic_calibrate_decr,
.progress = udbg_progress,
+#ifdef CONFIG_PPC64
+ .power_save = book3e_idle,
+#else
+ .power_save = e500_idle,
+#endif
};
--
2.25.1
next reply other threads:[~2022-01-12 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:24 Joachim Wiberg [this message]
2022-01-12 12:36 ` [PATCH 1/1] powerpc/e500/qemu-e500: allow core to idle without waiting Scott Wood
2022-01-14 10:32 ` Joachim Wiberg
2022-01-14 17:49 ` Scott Wood
2022-02-15 5:26 ` Michael Ellerman
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=20220112112459.1033754-1-troglobit@gmail.com \
--to=troglobit@gmail$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=oss@buserror$(echo .)net \
--cc=paulus@samba$(echo .)org \
--cc=tobias@waldekranz$(echo .)com \
/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