[U-Boot] [PATCH] ARMv8: Bug fix of dcache_disable()

[FengHua]

hi Mark,
    Thank you review this patch.

> -----Original Messages-----
> From: "Mark Rutland" <mark.rutland at arm.com>
> Sent Time: 2015-02-09 19:05:54 (Monday)
> To: "fenghua at phytium.com.cn" <fenghua at phytium.com.cn>
> Cc: "u-boot at lists.denx.de" <u-boot at lists.denx.de>
> Subject: Re: [U-Boot] [PATCH] ARMv8: Bug fix of dcache_disable()
> 
> On Mon, Feb 09, 2015 at 08:51:59AM +0000, fenghua at phytium.com.cn wrote:
> > From: David Feng <fenghua at phytium.com.cn>
> > 
> > The cache disable operation shoud be performed after flush_dcache_all().
> > If cache disable operation is performed before
> > flush_dcache_all(), flush_dcache_all() store data directly to memory
> > and may be overrided by data copy in cache.
> 
> The reasoning above (and hence this patch) is wrong.
> 
> While the caches are on, they can allocate lines for any portion of the
> address space with cacheable attributes, and can acquire dirty cache
> lines from other CPUs. Additionally, there is no restriction preventing
> lines from migrating between levels of cache while they are active.
> 
> So calling flush_dcache_all (which performs maintenance by Set/Way)
> while the caches are enabled is wrong. Per the architecture it provides
> no guarantee whatsoever.
> 
> To empty the caches by Set/Way, they must first be disabled. Note that
> this only guarantees that the caches are empty; not where the data went.
> Other CPUs might acquire dirty lines, or the data might only reach a
> system cache rather than memory.
> 
> If you need certain portions of data to be flushed out to memory, then
> those must be flushed by VA. If flush_dcache_all performs any memory
> accesses before it has completed Set/Way maintenance, it is buggy.
> 
> Thanks,
> Mark.
You are right. If data acess exist when flushing cache when cache is enabled,
the data may be brought to cache again. In normal circumstance we can not do
like this.
But the problem is flush_dcahe_all is a C routine, it will preserve return
address in stack. If disable cache first the return address will be directly
store in memory, and if the stack has a copy in cache the data will be covered
when flushing cache, then flush_dcache_all will get wrong return address.

There should be no data access between disabling cache and flushing cache.
U-boot for aarch64 runs at only one processor and the data flush_dcache_all manipulated
will not be used by following routines. By simply adjusting the sequence can fix this
bug although it's not the best solution.

Yours,
David.

> 
> > 
> > Signed-off-by: David Feng <fenghua at phytium.com.cn>
> > ---
> >  arch/arm/cpu/armv8/cache_v8.c |    3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/arch/arm/cpu/armv8/cache_v8.c b/arch/arm/cpu/armv8/cache_v8.c
> > index 9dbcdf2..dc2fc8c 100644
> > --- a/arch/arm/cpu/armv8/cache_v8.c
> > +++ b/arch/arm/cpu/armv8/cache_v8.c
> > @@ -124,9 +124,10 @@ void dcache_disable(void)
> >  	if (!(sctlr & CR_C))
> >  		return;
> >  
> > +	flush_dcache_all();
> > +
> >  	set_sctlr(sctlr & ~(CR_C|CR_M));
> >  
> > -	flush_dcache_all();
> >  	__asm_invalidate_tlb_all();
> >  }
> >  
> > -- 
> > 1.7.9.5
> > 
> > 
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
> >