From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greentime Hu Subject: Re: [PATCH v3 09/33] nds32: Cache and TLB routines Date: Wed, 13 Dec 2017 16:30:41 +0800 Message-ID: References: <9d0e976c3e60bf6834dffb6ef798ad2a03e1c9ac.1512723245.git.green.hu@gmail.com> <20171213021619.GA6254@gary-OptiPlex-3050> <20171213081949.GA18840@gary-OptiPlex-3050> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20171213081949.GA18840@gary-OptiPlex-3050> Sender: linux-arch-owner@vger.kernel.org To: Guo Ren Cc: Greentime , Linux Kernel Mailing List , Arnd Bergmann , linux-arch , Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , netdev , Vincent Chen , DTML , Al Viro , David Howells , Will Deacon , Daniel Lezcano , linux-serial@vger.kernel.org, Geert Uytterhoeven , Linus Walleij , Mark Rutland , Greg KH List-Id: devicetree@vger.kernel.org 2017-12-13 16:19 GMT+08:00 Guo Ren : > On Wed, Dec 13, 2017 at 01:45:02PM +0800, Greentime Hu wrote: > >> I think it should be fine if an interruption between mtsr_dsb and >> tlbop_rwr because this is a optimization by sw. > > Fine? When there is an unexpected vaddr in SR_TLB_VPN, tlbop_rwr(*pte) will > break that vaddr's pfn in the CPU tlb-buffer entry. When linux access the > vaddr, it will get wrong data unless the entry has been replaced out. Hi, Guo Ren: Thanks. I get your point. It is needed to be protected. I will fix it in the next version patch. if (vma->vm_mm == current->active_mm) { local_irq_save(flags); __nds32__mtsr_dsb(addr, NDS32_SR_TLB_VPN); __nds32__tlbop_rwr(*pte); __nds32__isb(); local_irq_restore(flags); }