Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp329133ybh; Fri, 6 Mar 2020 23:06:11 -0800 (PST) X-Google-Smtp-Source: ADFU+vs14Zx6b05fHouYnF91WAZsKYy6w2G0vhZBTmFQvCrHybj4OI5xd02M5tiT6pEoWfatzh0u X-Received: by 2002:aca:ef08:: with SMTP id n8mr96177oih.115.1583564771735; Fri, 06 Mar 2020 23:06:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583564771; cv=none; d=google.com; s=arc-20160816; b=ePJjCJ0KaqBvN5IhuG3LMObYdxX4OksPjx1GEvE+I82wPrbxjqWIhSQAbjMxhFkso3 aHl5W474j9VVl4QHkPRvEFDv+n3HKTPVTxIXP8pKvjKurZ5u7Uli2vZMIBbTBFg1MrWp GpZgOfvGlWRmQdebDqJ6AlRYXfJIFx0wj6znwoqQv678LMpMRxc7VeqQv8AovXwfkFpx 7BLrppkAVsrGHoujKF9nP8bHHrD1hvztpwVtlHD7CmiI21GPOvhCBy/0QiH7FSkVhKlQ pg/cpQbq13u7esYAx0By7659BpZNh6RM+IX7QYK6C+aFNe2YRaOHrtPV0kEmwieZsKFy 00aw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=KLykoiwakmvXlj7iOgiNeBA+k4S6on8FDV27weKg6MI=; b=eylkry0J83L6o/S85rYpXd4jVByutVYj9ckZ5ASx5CzNceIhK94jPu5AtdsvJ38mVc 0GhhZW4QZU5Ca2aYyiDAatMvW6yHNWEsyGwFlQxrxF9alGTf447576hfag0nXrQoCEDH XgCvfyNf3a47HxrY7CIEwR785QhAFpyGil0qx2X+SDY882KEKMoH78xvjLf9UIML8tg2 aA+GmgGjpjNblmAv9gAUiz+kQgdoUQhyp13/UKq/pl/cWQC7PLUFsS77psFUUOaTemuM 3ZFtsdtJzTa+/LFdpQxlVm04ve9C2yjHuPkRRujfPaeQNcZTaQ5B9ugjMuaboFH+KgB4 DoYg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=hFwvKFlt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n26si2822058otr.78.2020.03.06.23.05.48; Fri, 06 Mar 2020 23:06:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=hFwvKFlt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726102AbgCGHFO (ORCPT + 99 others); Sat, 7 Mar 2020 02:05:14 -0500 Received: from pegase1.c-s.fr ([93.17.236.30]:2841 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725907AbgCGHFO (ORCPT ); Sat, 7 Mar 2020 02:05:14 -0500 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 48ZFqW22V5zB09Zy; Sat, 7 Mar 2020 08:05:11 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=hFwvKFlt; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id JH70JFMo2Nhm; Sat, 7 Mar 2020 08:05:11 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 48ZFqW06j2zB09Zx; Sat, 7 Mar 2020 08:05:11 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1583564711; bh=KLykoiwakmvXlj7iOgiNeBA+k4S6on8FDV27weKg6MI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=hFwvKFlt5tItEoeChiMcVbq8Z6WEJiAIueL914VqsjAkNiTW/tX4E4mkXgZPRPVQp 1TSwGC1wl0uEf1SM3tvrvXA0/srRG2BvZ2uOnFi+rWlXqmPEgF9Of2NNwJRqkfVxFW 8RUJEw8G1tWI+NWaS36EliXDmOzscoTf3q3gSbXQ= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id D550D8B784; Sat, 7 Mar 2020 08:05:11 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id OhKGFoGl11OV; Sat, 7 Mar 2020 08:05:11 +0100 (CET) Received: from [192.168.4.90] (unknown [192.168.4.90]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 4A0DC8B776; Sat, 7 Mar 2020 08:05:09 +0100 (CET) Subject: Re: [PATCH V15] mm/debug: Add tests validating architecture page table helpers To: Anshuman Khandual , Qian Cai Cc: linux-mm@kvack.org, Andrew Morton , Mike Rapoport , Vineet Gupta , Catalin Marinas , Will Deacon , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , "Kirill A . Shutemov" , Paul Walmsley , Palmer Dabbelt , linux-snps-arc@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-riscv@lists.infradead.org, x86@kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org References: <61250cdc-f80b-2e50-5168-2ec67ec6f1e6@arm.com> From: Christophe Leroy Message-ID: Date: Sat, 7 Mar 2020 08:05:09 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 07/03/2020 à 01:56, Anshuman Khandual a écrit : > > > On 03/07/2020 06:04 AM, Qian Cai wrote: >> >> >>> On Mar 6, 2020, at 7:03 PM, Anshuman Khandual wrote: >>> >>> Hmm, set_pte_at() function is not preferred here for these tests. The idea >>> is to avoid or atleast minimize TLB/cache flushes triggered from these sort >>> of 'static' tests. set_pte_at() is platform provided and could/might trigger >>> these flushes or some other platform specific synchronization stuff. Just >> >> Why is that important for this debugging option? > > Primarily reason is to avoid TLB/cache flush instructions on the system > during these tests that only involve transforming different page table > level entries through helpers. Unless really necessary, why should it > emit any TLB/cache flush instructions ? What's the problem with thoses flushes ? > >> >>> wondering is there specific reason with respect to the soft lock up problem >>> making it necessary to use set_pte_at() rather than a simple WRITE_ONCE() ? >> >> Looks at the s390 version of set_pte_at(), it has this comment, >> vmaddr); >> >> /* >> * Certain architectures need to do special things when PTEs >> * within a page table are directly modified. Thus, the following >> * hook is made available. >> */ >> >> I can only guess that powerpc could be the same here. > > This comment is present in multiple platforms while defining set_pte_at(). > Is not 'barrier()' here alone good enough ? Else what exactly set_pte_at() > does as compared to WRITE_ONCE() that avoids the soft lock up, just trying > to understand. > Argh ! I didn't realise that you were writing directly into the page tables. When it works, that's only by chance I guess. To properly set the page table entries, set_pte_at() has to be used: - On powerpc 8xx, with 16k pages, the page table entry must be copied four times. set_pte_at() does it, WRITE_ONCE() doesn't. - On powerpc book3s/32 (hash MMU), the flag _PAGE_HASHPTE must be preserved among writes. set_pte_at() preserves it, WRITE_ONCE() doesn't. set_pte_at() also does a few other mandatory things, like calling pte_mkpte() So, the WRITE_ONCE() must definitely become a set_pte_at() Christophe