Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp4149466pxv; Mon, 26 Jul 2021 23:16:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy/3qnbIjOH4HVA4HlnWOhuh8FXxaAXIfzFmLwnr+rtprF+B0+E/8gHZx1bhJ2zn2giiIPi X-Received: by 2002:a05:6402:1595:: with SMTP id c21mr18504478edv.354.1627366585823; Mon, 26 Jul 2021 23:16:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627366585; cv=none; d=google.com; s=arc-20160816; b=TQchzkC8ie/NgG6PCGygulz4ov7InIZe4wK2q5xBLEJW3LOpB3xePzpQf4/ilP4dZ8 EL5dJJs9DZYa/sABR9XFlde9QYbTGKY37WNeNc7JZj0hSJUITSgUW4bBhyQARdTm1vBo Pc6zTWe92RbK4ZTGZeZGrDHdGjzBTneuWvMcGczEqFld4TFdkEK+XVIRiRSydAL9+WSm lNyGT05mpgXcFa71OznDV7tmBLljoOWFInYl4CgoCOF6cpvvuAjkcRj1U/qeh2iGIrnK /juW8mR6M+AL7lLzPzhmo1rkvWco17wiOsluS2rtpHyrBRO3q4CktLtyRoGbun3WflB5 5PPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=+foQI4ZSsPugMdNXFeoThHY1y2soLUHl8MsBlGsSC9w=; b=fAotcsRgku7VPLeAAnN3D3dqjhXaLw9VDuBsV7HuS83fwlKfMbiuF2l6UGYeroOPXs OCvxrfs0bxYvr18R0uXPLtC7cY2hPNlszZYYN6+Fu5yrKOfLTcnHFX8dGTquOdX/wivd 1se3jhq5Stp+ocJ1she20I/09VfxBm8bzqHSaPKVWpK99vGYATDPusDgGa7Ua8QXhZJU TeelMlFdS++XeZpJPpixKhRTJw1byBeDiDhdvqgQcTyS1xuEYmvtzPE8tsJCNPM8T6pE clDuy80DgjGLZcpacNVNu1itef3jO8PyxCN9nK3MdPLMjY6wCU7MEYFyWA8HEEU8J2zB F5Dw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VZjIH65R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hq29si2077849ejc.133.2021.07.26.23.16.03; Mon, 26 Jul 2021 23:16:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VZjIH65R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235663AbhG0GOZ (ORCPT + 99 others); Tue, 27 Jul 2021 02:14:25 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:30743 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235657AbhG0GOW (ORCPT ); Tue, 27 Jul 2021 02:14:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1627366462; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=+foQI4ZSsPugMdNXFeoThHY1y2soLUHl8MsBlGsSC9w=; b=VZjIH65RteOPDJ1SiOkiLrEOe5j8tQazxSkThcqW2v5XzPVOYglXmdkZ2U5BZGcAz3tXDS XfG1O5fN1UNQoL54jOlOEJmeAO6IlrcvD/igP0SboxGMcqhHclg4RYxCRHEGlyuXyfJ9nT 5tuV+qaceJkoN5ypkAA6MjorwrQyCO4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-420-5jVv41_vN4Sao7o0MMzQKg-1; Tue, 27 Jul 2021 02:14:21 -0400 X-MC-Unique: 5jVv41_vN4Sao7o0MMzQKg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8806D100E420; Tue, 27 Jul 2021 06:14:19 +0000 (UTC) Received: from gshan.redhat.com (vpn2-54-195.bne.redhat.com [10.64.54.195]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 60234687D5; Tue, 27 Jul 2021 06:14:13 +0000 (UTC) From: Gavin Shan To: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org, anshuman.khandual@arm.com, gerald.schaefer@linux.ibm.com, aneesh.kumar@linux.ibm.com, christophe.leroy@csgroup.eu, cai@lca.pw, catalin.marinas@arm.com, will@kernel.org, akpm@linux-foundation.org, chuhu@redhat.com, shan.gavin@gmail.com Subject: [PATCH v4 00/12] mm/debug_vm_pgtable: Enhancements Date: Tue, 27 Jul 2021 14:13:49 +0800 Message-Id: <20210727061401.592616-1-gshan@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There are couple of issues with current implementations and this series tries to resolve the issues: (a) All needed information are scattered in variables, passed to various test functions. The code is organized in pretty much relaxed fashion. (b) The page isn't allocated from buddy during page table entry modifying tests. The page can be invalid, conflicting to the implementations of set_xxx_at() on ARM64. The target page is accessed so that the iCache can be flushed when execution permission is given on ARM64. Besides, the target page can be unmapped and access to it causes kernel crash. "struct pgtable_debug_args" is introduced to address issue (a). For issue (b), the used page is allocated from buddy in page table entry modifying tests. The corresponding tets will be skipped if we fail to allocate the (huge) page. For other test cases, the original page around to kernel symbol (@start_kernel) is still used. The patches are organized as below. PATCH[2-10] could be combined to one patch, but it will make the review harder: PATCH[1] introduces "struct pgtable_debug_args" as place holder of all needed information. With it, the old and new implementation can coexist. PATCH[2-10] uses "struct pgtable_debug_args" in various test functions. PATCH[11] removes the unused code for old implementation. PATCH[12] fixes the issue of corrupted page flag for ARM64 Changelog ========= v4: * Determine the page allocation method according to MAX_ORDER (Anshuman) * Move existing comments to init_args() (Anshuman) * Code refactoring as suggested by Anshuman (Anshuman) * Improved commit log and add comments for flush_dcache_page() in PATCH[v4 12/12] (Anshuman) * Address misc comments (Anshuman) v3: * Fix the warning caused by allocating more pages than (1 << (MAX_ORDER - 1)) in init_args() (syzbot) * Fix build warning by dropping unused variables in separate patches (0-day) * Missed "WARN_ON(!pud_none(pud))" in pud_huge_tests() in PATCH[v2 09/12] (0-day) * Fix the subjects for PATCH[05/12] and PATCH[09/12] (Gavin) v2: * Rename struct vm_pgtable_debug to struct pgtable_debug_args. The parameter name to various test functions are renamed to "@args" (Anshuman) * Code changes as suggested by Anshuman (Anshuman) Gavin Shan (12): mm/debug_vm_pgtable: Introduce struct pgtable_debug_args mm/debug_vm_pgtable: Use struct pgtable_debug_args in basic tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in leaf and savewrite tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in protnone and devmap tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in soft_dirty and swap tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in migration and thp tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PTE modifying tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PMD modifying tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PUD modifying tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PGD and P4D modifying tests mm/debug_vm_pgtable: Remove unused code mm/debug_vm_pgtable: Fix corrupted page flag mm/debug_vm_pgtable.c | 919 ++++++++++++++++++++++++++---------------- 1 file changed, 566 insertions(+), 353 deletions(-) -- 2.23.0