linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com, npiggin@gmail.com, anton@samba.org
Subject: Re: powerpc/mm/radix: Drop support for CPUs without lockless tlbie
Date: Thu,  4 May 2017 08:19:03 +1000 (AEST)	[thread overview]
Message-ID: <3wJCHW665Wz9s03@ozlabs.org> (raw)
In-Reply-To: <1493786699-14850-1-git-send-email-mpe@ellerman.id.au>

On Wed, 2017-05-03 at 04:44:59 UTC, Michael Ellerman wrote:
> Currently the radix TLB code includes support for CPUs that do *not*
> have MMU_FTR_LOCKLESS_TLBIE. On those CPUs we are required to take a
> global spinlock before issuing a tlbie.
> 
> Radix can only be built for 64-bit Book3s CPUs, and of those, only
> POWER4, 970, Cell and PA6T do not have MMU_FTR_LOCKLESS_TLBIE. Although
> it's possible to build a kernel with Radix support that can also boot on
> those CPUs, we happen to know that in reality none of those CPUs support
> the Radix MMU, so the code can never actually run on those CPUs.
> 
> So remove the native_tlbie_lock in the Radix TLB code.
> 
> Note that there is another lock of the same name in the hash code, which
> is unaffected by this patch.
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>

Applied to powerpc next.

https://git.kernel.org/powerpc/c/3c9ac2bcc35453141f82461c71ed10

cheers

      parent reply	other threads:[~2017-05-03 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03  4:44 [PATCH] powerpc/mm/radix: Drop support for CPUs without lockless tlbie Michael Ellerman
2017-05-03  5:36 ` Nicholas Piggin
2017-05-03 22:19 ` 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=3wJCHW665Wz9s03@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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).