From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/64: don't select ARCH_HAS_SCALED_CPUTIME on book3E
Date: Wed, 28 Aug 2019 14:24:50 +1000 (AEST) [thread overview]
Message-ID: <46JCM65tstz9sP9@ozlabs.org> (raw)
In-Reply-To: <a8b567c569aa521a7cf1beb061d43d79070e850c.1566492229.git.christophe.leroy@c-s.fr>
On Thu, 2019-08-22 at 16:44:05 UTC, Christophe Leroy wrote:
> Book3E doesn't have SPRN_SPURR/SPRN_PURR.
>
> Activating ARCH_HAS_SCALED_CPUTIME is just wasting CPU time.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
> Link: https://github.com/linuxppc/issues/issues/171
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b4645ffc49cfe34f67feda20c34bd7a859c78312
cheers
prev parent reply other threads:[~2019-08-28 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 16:44 [PATCH] powerpc/64: don't select ARCH_HAS_SCALED_CPUTIME on book3E Christophe Leroy
2019-08-28 4:24 ` Michael Ellerman [this message]
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=46JCM65tstz9sP9@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
/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).