All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Oliver O'Halloran <oohall@gmail.com>,
	Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] powerpc/64: flush_inval_dcache_range() becomes flush_dcache_range()
Date: Mon,  8 Jul 2019 11:19:31 +1000 (AEST)	[thread overview]
Message-ID: <45hnfq75mmz9sNF@ozlabs.org> (raw)
In-Reply-To: <239d1c8f15b8bedc161a234f9f1a22a07160dbdf.1557824379.git.christophe.leroy@c-s.fr>

On Tue, 2019-05-14 at 09:05:13 UTC, Christophe Leroy wrote:
> On most arches having function flush_dcache_range(), including PPC32,
> this function does a writeback and invalidation of the cache bloc.
> 
> On PPC64, flush_dcache_range() only does a writeback while
> flush_inval_dcache_range() does the invalidation in addition.
> 
> In addition it looks like within arch/powerpc/, there are no PPC64
> platforms using flush_dcache_range()
> 
> This patch drops the existing 64 bits version of flush_dcache_range()
> and renames flush_inval_dcache_range() into flush_dcache_range().
> 
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/1cfb725fb1899dc6fdc88f8b5354a65e8ad260c6

cheers

      parent reply	other threads:[~2019-07-08  1:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  9:05 [PATCH 1/4] powerpc/64: flush_inval_dcache_range() becomes flush_dcache_range() Christophe Leroy
2019-05-14  9:05 ` Christophe Leroy
2019-05-14  9:05 ` [PATCH 2/4] powerpc/32: activate ARCH_HAS_PMEM_API and ARCH_HAS_UACCESS_FLUSHCACHE Christophe Leroy
2019-05-14  9:05   ` Christophe Leroy
2019-07-15  6:49   ` Michael Ellerman
2019-07-15  6:49     ` Michael Ellerman
2019-07-15  7:02     ` Oliver O'Halloran
2019-07-15  7:02       ` Oliver O'Halloran
2019-07-15 17:03     ` Christophe Leroy
2019-07-15 17:03       ` Christophe Leroy
2019-05-14  9:05 ` [PATCH 3/4] powerpc/32: define helpers to get L1 cache sizes Christophe Leroy
2019-05-14  9:05   ` Christophe Leroy
2019-07-08  1:19   ` Michael Ellerman
2019-05-14  9:05 ` [PATCH 4/4] powerpc/64: reuse PPC32 static inline flush_dcache_range() Christophe Leroy
2019-05-14  9:05   ` Christophe Leroy
2019-07-08  1:19   ` Michael Ellerman
2019-07-08 14:21   ` Aneesh Kumar K.V
2019-07-08 14:21     ` Aneesh Kumar K.V
2019-07-09  2:20     ` Oliver O'Halloran
2019-07-09  2:20       ` Oliver O'Halloran
2019-07-09  2:51       ` Aneesh Kumar K.V
2019-07-09  2:51         ` Aneesh Kumar K.V
2019-07-09  5:29         ` Oliver O'Halloran
2019-07-09  5:29           ` Oliver O'Halloran
2019-07-09 17:04         ` Segher Boessenkool
2019-07-09 17:04           ` Segher Boessenkool
2019-08-08  6:53   ` powerpc flush_inval_dcache_range() was buggy until v5.3-rc1 (was Re: [PATCH 4/4] powerpc/64: reuse PPC32 static inline flush_dcache_range()) Michael Ellerman
2019-08-08  6:53     ` Michael Ellerman
2019-07-08  1: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=45hnfq75mmz9sNF@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=oohall@gmail.com \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.