From: Scott Wood <scottwood@freescale.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: Chenhui Zhao <chenhui.zhao@freescale.com>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v3 1/6] powerpc/mm: any thread in one core can be the first to setup TLB1
Date: Fri, 4 Dec 2015 13:48:21 -0600 [thread overview]
Message-ID: <1449258501.15946.47.camel@freescale.com> (raw)
In-Reply-To: <CAOJe8K1Lmc4oceW1gLuwXsrLgzg=YgVbsVTzQgqm6yp+vSbM6w@mail.gmail.com>
On Fri, 2015-12-04 at 11:04 +0300, Denis Kirjanov wrote:
> On 12/3/15, Scott Wood <scottwood@freescale.com> wrote:
> > On Wed, 2015-12-02 at 15:12 +0300, Denis Kirjanov wrote:
> > > On 11/20/15, Chenhui Zhao <chenhui.zhao@freescale.com> wrote:
> > > > On e6500, in the case of cpu hotplug, either thread in one core
> > > > may be the first thread initilzing the TLB1. The subsequent threads
> > > > must not setup it again.
> > > >
> > > > The code is derived from the comment of Scott Wood.
> > > >
> > > > Signed-off-by: Chenhui Zhao <chenhui.zhao@freescale.com>
> > > > ---
> > > > arch/powerpc/include/asm/cputhreads.h | 7 +++++++
> > > > arch/powerpc/mm/tlb_nohash.c | 4 +---
> > > > 2 files changed, 8 insertions(+), 3 deletions(-)
> > > >
> > > > diff --git a/arch/powerpc/include/asm/cputhreads.h
> > > > b/arch/powerpc/include/asm/cputhreads.h
> > > > index ba42e46..b56cece 100644
> > > > --- a/arch/powerpc/include/asm/cputhreads.h
> > > > +++ b/arch/powerpc/include/asm/cputhreads.h
> > > > @@ -94,6 +94,13 @@ static inline int cpu_last_thread_sibling(int cpu)
> > > > return cpu | (threads_per_core - 1);
> > > > }
> > > >
> > > > +static inline u32 get_tensr(void)
> > > > +{
> > > > + if (cpu_has_feature(CPU_FTR_SMT))
> > > > + return mfspr(SPRN_TENSR);
> > > > + else
> > > > + return 1;
> > > > +}
> > > If i get it right, SPRN_TENSR used in the code only if CONFIG_PPC64
> > > is defined. Then we can make it noop on ppc32.
> >
> > Please don't. It accomplishes nothing other than adding an obstacle to
> > supporting this on ppc32.
>
> The idea is make it noop since the function defined in header file and
> some core parts include it like:
>
> arch/powerpc/kernel/smp.c
> arch/powerpc/kernel/setup-common.c
What does that have to do with making it a no-op on 32-bit? I understand
ifdeffing on CONFIG_BOOKE due to the build issue, but not CONFIG_PPC64.
-Scott
prev parent reply other threads:[~2015-12-04 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 9:13 [PATCH v3 1/6] powerpc/mm: any thread in one core can be the first to setup TLB1 Chenhui Zhao
2015-11-20 9:13 ` [PATCH v3 2/6] powerpc/cache: add cache flush operation for various e500 Chenhui Zhao
2015-11-20 9:13 ` [PATCH v3 3/6] powerpc/rcpm: add RCPM driver Chenhui Zhao
2015-11-20 9:14 ` [PATCH v3 4/6] powerpc/mpc85xx: refactor the PM operations Chenhui Zhao
2015-11-20 9:14 ` [PATCH v3 5/6] powerpc/mpc85xx: Add hotplug support on E5500 and E500MC cores Chenhui Zhao
2015-11-20 9:14 ` [PATCH v3 6/6] powerpc/mpc85xx: Add CPU hotplug support for E6500 Chenhui Zhao
2015-12-02 11:04 ` [PATCH v3 1/6] powerpc/mm: any thread in one core can be the first to setup TLB1 Chenhui Zhao
2015-12-02 12:12 ` Denis Kirjanov
2015-12-03 11:27 ` Chenhui Zhao
2015-12-23 21:27 ` Scott Wood
2015-12-24 0:47 ` Zhao C.H.
2015-12-03 19:26 ` Scott Wood
2015-12-04 8:04 ` Denis Kirjanov
2015-12-04 19:48 ` Scott Wood [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=1449258501.15946.47.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=chenhui.zhao@freescale.com \
--cc=kda@linux-powerpc.org \
--cc=linuxppc-dev@lists.ozlabs.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).