mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alastair D'Silva" <alastair@au1.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Qian Cai <cai@lca.pw>, Thomas Gleixner <tglx@linutronix.de>,
	Nicholas Piggin <npiggin@gmail.com>,
	Allison Randal <allison@lohutok.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>,
	David Hildenbrand <david@redhat.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] powerpc: Allow flush_icache_range to work across ranges >4GB
Date: Thu, 19 Sep 2019 13:48:38 +1000	[thread overview]
Message-ID: <cdc29892276ea4c8a83739b79fb6d8b286f319ba.camel@au1.ibm.com> (raw)
In-Reply-To: <87imppuf0w.fsf@mpe.ellerman.id.au>

On Thu, 2019-09-19 at 13:43 +1000, Michael Ellerman wrote:
> "Alastair D'Silva" <alastair@au1.ibm.com> writes:
> > From: Alastair D'Silva <alastair@d-silva.org>
> > 
> > When calling flush_icache_range with a size >4GB, we were masking
> > off the upper 32 bits, so we would incorrectly flush a range
> > smaller
> > than intended.
> > 
> > __kernel_sync_dicache in the 64 bit VDSO has the same bug.
> 
> Please fix that in a separate patch.
> 
> Your subject doesn't mention __kernel_sync_dicache(), and also the
> two
> changes backport differently, so it's better if they're done as
> separate
> patches.
> 

Ok.

> cheers
> 
> > This patch replaces the 32 bit shifts with 64 bit ones, so that
> > the full size is accounted for.
> > 
> > Signed-off-by: Alastair D'Silva <alastair@d-silva.org>
> > Cc: stable@vger.kernel.org
> > ---
> >  arch/powerpc/kernel/misc_64.S           | 4 ++--
> >  arch/powerpc/kernel/vdso64/cacheflush.S | 4 ++--
> >  2 files changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/arch/powerpc/kernel/misc_64.S
> > b/arch/powerpc/kernel/misc_64.S
> > index b55a7b4cb543..9bc0aa9aeb65 100644
> > --- a/arch/powerpc/kernel/misc_64.S
> > +++ b/arch/powerpc/kernel/misc_64.S
> > @@ -82,7 +82,7 @@ END_FTR_SECTION_IFSET(CPU_FTR_COHERENT_ICACHE)
> >  	subf	r8,r6,r4		/* compute length */
> >  	add	r8,r8,r5		/* ensure we get enough */
> >  	lwz	r9,DCACHEL1LOGBLOCKSIZE(r10)	/* Get log-2 of cache block
> > size */
> > -	srw.	r8,r8,r9		/* compute line count */
> > +	srd.	r8,r8,r9		/* compute line count */
> >  	beqlr				/* nothing to do? */
> >  	mtctr	r8
> >  1:	dcbst	0,r6
> > @@ -98,7 +98,7 @@ END_FTR_SECTION_IFSET(CPU_FTR_COHERENT_ICACHE)
> >  	subf	r8,r6,r4		/* compute length */
> >  	add	r8,r8,r5
> >  	lwz	r9,ICACHEL1LOGBLOCKSIZE(r10)	/* Get log-2 of Icache
> > block size */
> > -	srw.	r8,r8,r9		/* compute line count */
> > +	srd.	r8,r8,r9		/* compute line count */
> >  	beqlr				/* nothing to do? */
> >  	mtctr	r8
> >  2:	icbi	0,r6
> > diff --git a/arch/powerpc/kernel/vdso64/cacheflush.S
> > b/arch/powerpc/kernel/vdso64/cacheflush.S
> > index 3f92561a64c4..526f5ba2593e 100644
> > --- a/arch/powerpc/kernel/vdso64/cacheflush.S
> > +++ b/arch/powerpc/kernel/vdso64/cacheflush.S
> > @@ -35,7 +35,7 @@ V_FUNCTION_BEGIN(__kernel_sync_dicache)
> >  	subf	r8,r6,r4		/* compute length */
> >  	add	r8,r8,r5		/* ensure we get enough */
> >  	lwz	r9,CFG_DCACHE_LOGBLOCKSZ(r10)
> > -	srw.	r8,r8,r9		/* compute line count */
> > +	srd.	r8,r8,r9		/* compute line count */
> >  	crclr	cr0*4+so
> >  	beqlr				/* nothing to do? */
> >  	mtctr	r8
> > @@ -52,7 +52,7 @@ V_FUNCTION_BEGIN(__kernel_sync_dicache)
> >  	subf	r8,r6,r4		/* compute length */
> >  	add	r8,r8,r5
> >  	lwz	r9,CFG_ICACHE_LOGBLOCKSZ(r10)
> > -	srw.	r8,r8,r9		/* compute line count */
> > +	srd.	r8,r8,r9		/* compute line count */
> >  	crclr	cr0*4+so
> >  	beqlr				/* nothing to do? */
> >  	mtctr	r8
> > -- 
> > 2.21.0
-- 
Alastair D'Silva
Open Source Developer
Linux Technology Centre, IBM Australia
mob: 0423 762 819


  reply	other threads:[~2019-09-19  3:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18  5:20 [PATCH v3 0/5] powerpc: convert cache asm to C Alastair D'Silva
2019-09-18  5:20 ` [PATCH v3 1/5] powerpc: Allow flush_icache_range to work across ranges >4GB Alastair D'Silva
2019-09-19  3:43   ` Michael Ellerman
2019-09-19  3:48     ` Alastair D'Silva [this message]
2019-09-18  5:20 ` [PATCH v3 2/5] powerpc: define helpers to get L1 icache sizes Alastair D'Silva
2019-09-18  5:20 ` [PATCH v3 3/5] powerpc: Convert flush_icache_range & friends to C Alastair D'Silva
2019-09-18  5:20 ` [PATCH v3 4/5] powerpc: Chunk calls to flush_dcache_range in arch_*_memory Alastair D'Silva
2019-09-18  5:20 ` [PATCH v3 5/5] powerpc: Don't flush caches when adding memory Alastair D'Silva

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=cdc29892276ea4c8a83739b79fb6d8b286f319ba.camel@au1.ibm.com \
    --to=alastair@au1.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=allison@lohutok.net \
    --cc=benh@kernel.crashing.org \
    --cc=cai@lca.pw \
    --cc=christophe.leroy@c-s.fr \
    --cc=david@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhocko@suse.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®