public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
	linuxppc-dev@lists•ozlabs.org
Cc: aneesh.kumar@linux•vnet.ibm.com
Subject: Re: [v2, 1/4] powerpc/mm/radix: Improve _tlbiel_pid to be usable for PWC flushes
Date: Mon,  7 Aug 2017 20:41:50 +1000 (AEST)	[thread overview]
Message-ID: <3xQvGl00QXz9t2S@ozlabs.org> (raw)
In-Reply-To: <20170719044907.21703-1-benh@kernel.crashing.org>

On Wed, 2017-07-19 at 04:49:04 UTC, Benjamin Herrenschmidt wrote:
> The PWC flush only needs a single set call, just like the
> full (RIC=2) flush.
> 
> This will allow us to get rid of the dedicated _tlbiel_pwc()
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux•vnet.ibm.com>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/5ce5fe14ed0302315061cf97ce67ac

cheers

      parent reply	other threads:[~2017-08-07 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19  4:49 [PATCH v2 1/4] powerpc/mm/radix: Improve _tlbiel_pid to be usable for PWC flushes Benjamin Herrenschmidt
2017-07-19  4:49 ` [PATCH v2 2/4] powerpc/mm/radix: Improve TLB/PWC flushes Benjamin Herrenschmidt
2017-07-20  2:52   ` Aneesh Kumar K.V
2017-07-19  4:49 ` [PATCH v2 3/4] powerpc/mm/radix: Avoid flushing the PWC on every flush_tlb_range Benjamin Herrenschmidt
2017-07-20  2:52   ` Aneesh Kumar K.V
2017-07-19  4:49 ` [PATCH v2 4/4] powerpc/mm/radix: Workaround prefetch issue with KVM Benjamin Herrenschmidt
2017-07-20  2:51 ` [PATCH v2 1/4] powerpc/mm/radix: Improve _tlbiel_pid to be usable for PWC flushes Aneesh Kumar K.V
2017-08-07 10:41 ` 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=3xQvGl00QXz9t2S@ozlabs.org \
    --to=patch-notifications@ellerman$(echo .)id.au \
    --cc=aneesh.kumar@linux$(echo .)vnet.ibm.com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /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