From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Nicholas Piggin <npiggin@gmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH 0/3] powerpc/32: nohz full support
Date: Tue, 4 Oct 2022 11:58:30 +0000 [thread overview]
Message-ID: <f728293c-7176-e564-7db9-4c8d30edfcfd@csgroup.eu> (raw)
In-Reply-To: <20221004063306.511154-1-npiggin@gmail.com>
Le 04/10/2022 à 08:33, Nicholas Piggin a écrit :
> Doesn't seem to be much more involved in adding context tracking and
> generic virt cpu accounting support for 32-bit, which is all that's
> left to support NO_HZ_FULL.
>
> I tested this with e5500 SMP kernel with isolated and nohz CPU, and
> it seems to be doing the right thing -- periodic tick is stopped on
> the nohz CPUs when they are running in userspace.
>
> Context tracking warnings should catch quite quickly if we got
> something wrong there (with the force context tracking option). I
> don't have a 32-bit KVM environment to test so that might have some
> issues but it should be quite easy to fix if it can be tested.
>
> I assume the virt cpu accounting gen option removal is okay, but not
> exactly sure what to look for in terms of possible problems, so we'll
> see what comments that gets back.
I'm having hard time finding the link between patch 1 and patch 2/3.
Christophe
>
> Thanks,
> Nick
>
> Nicholas Piggin (3):
> powerpc/32: Implement HAVE_CONTEXT_TRACKING_USER support
> powerpc: remove the last remnants of cputime_t
> Remove HAVE_VIRT_CPU_ACCOUNTING_GEN option
>
> arch/Kconfig | 11 -----------
> arch/arm/Kconfig | 1 -
> arch/csky/Kconfig | 1 -
> arch/loongarch/Kconfig | 1 -
> arch/mips/Kconfig | 1 -
> arch/powerpc/Kconfig | 2 +-
> arch/powerpc/include/asm/cputime.h | 17 +----------------
> arch/powerpc/include/asm/interrupt.h | 21 ++++++---------------
> arch/powerpc/kernel/time.c | 23 ++---------------------
> arch/xtensa/Kconfig | 1 -
> init/Kconfig | 1 -
> kernel/time/Kconfig | 2 --
> 12 files changed, 10 insertions(+), 72 deletions(-)
>
next prev parent reply other threads:[~2022-10-04 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 6:33 [RFC PATCH 0/3] powerpc/32: nohz full support Nicholas Piggin
2022-10-04 6:33 ` [RFC PATCH 1/3] powerpc/32: Implement HAVE_CONTEXT_TRACKING_USER support Nicholas Piggin
2022-10-04 11:32 ` Christophe Leroy
2022-10-06 8:22 ` Nicholas Piggin
2022-10-04 6:33 ` [RFC PATCH 2/3] powerpc: remove the last remnants of cputime_t Nicholas Piggin
2022-10-06 10:06 ` Michael Ellerman
2022-10-04 6:33 ` [RFC PATCH 3/3] Remove HAVE_VIRT_CPU_ACCOUNTING_GEN option Nicholas Piggin
2022-10-04 11:58 ` Christophe Leroy [this message]
2022-10-06 8:18 ` [RFC PATCH 0/3] powerpc/32: nohz full support Nicholas Piggin
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=f728293c-7176-e564-7db9-4c8d30edfcfd@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).