Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1210994pxf; Fri, 2 Apr 2021 04:27:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx0iODsyDiwQi+LTEewFF0vQZmXNEeSTwlMxCtmxYAR4XJcBCtt27zyKZXnVdLkRcVTBoNe X-Received: by 2002:a05:6402:5203:: with SMTP id s3mr15157506edd.79.1617362872447; Fri, 02 Apr 2021 04:27:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617362872; cv=none; d=google.com; s=arc-20160816; b=eGUtbbhjqqOHX5QrZS0rGPPpSz01HsMcHIc5HP1H/wnTTKOS6bQzxZrIwmBPJ22iHY V51H9VxCTU/hcjRiZcAqeiMHndrR5oX/DeS+WlZId/9VAVUnP00P+L80SZeTj4jNwkK/ UMX56IzmdS/YGqKmRnqEtUViYzfTjMmY4U7/f8zXzcHVz7qJyqYNyFQITgG0SiW4DLrw HzpAQi3wepIxnLMDEsGVj3pJAvYnAmaCuUIUSeoJ/g7WhZOPSbAWr6uZ2YYaOlYMHQ7s 1xDxWtGZ8GmL30hxNWqvLENf5ShXRCnOOLpuGRKvD3TMizBiR417vBzTdwx3oooQIn8B BkLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=5TJQKuTy4aNhykmUPeVuq8Z8E02ia8vCzCmWP10DlHw=; b=DTj6j2/M1a+l79u76WPBfFS+m58t6B8RMy3Po5f3GxmdtijHf4O1JztUlc/lhZQpC1 dXO0Poayu9d13a/CaSc9r4DBpasNbFBQctatTgva9MMVm4jMsTBmaun7TtAtIl8Y/lAu X9YECoIR7nJ3NaDWjzoof22Q+cZKJp8mJ/jEi7xE63BElY9L4Bz5/9te5vJF09BTNomy 4HNhP1s/H10EoZPfNal71PQBDbcJQMCX2At40DbE8caS8ZJRCgMa5X/uEwenRXFk/oSG 2ReIgQS2lNaM4FBDJNefjVUq0a52zIOAVM5d5tjlyvynL4pRCiUIFuHrsPF27VCw67uV Js8g== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u10si6188190ejg.204.2021.04.02.04.27.29; Fri, 02 Apr 2021 04:27:52 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234207AbhDBL1E (ORCPT + 99 others); Fri, 2 Apr 2021 07:27:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:36262 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229599AbhDBL1C (ORCPT ); Fri, 2 Apr 2021 07:27:02 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 32EB4610CF; Fri, 2 Apr 2021 11:27:00 +0000 (UTC) Date: Fri, 2 Apr 2021 12:26:57 +0100 From: Catalin Marinas To: Zack Rusin Cc: linux-kernel@vger.kernel.org, Will Deacon , Peter Zijlstra , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64/mm: Fix mapping_dirty_helpers with arm64 Message-ID: <20210402112657.GB29774@arm.com> References: <20210331182344.47987-1-zackr@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210331182344.47987-1-zackr@vmware.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 31, 2021 at 02:23:44PM -0400, Zack Rusin wrote: > The pagetable walk callbacks in mm/mapping_dirty_helpers.c depend > on a set of helpers from which pud_dirty(pud) was missing. I'm > assuming mapping_dirty_helpers weren't used on ARM64 before > because the missing pud_dirty is causing a compilation error. > > The drivers/gpu/drm/vmwgfx code uses mapping_dirty_helpers and > has been ported to ARM64 but it depends on this code getting in > first in order to compile/work. > > Cc: Catalin Marinas > Cc: Will Deacon > Cc: Peter Zijlstra > Cc: linux-arm-kernel@lists.infradead.org > Signed-off-by: Zack Rusin > --- > arch/arm64/include/asm/pgtable.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h > index 47027796c2f9..ecd80f87a996 100644 > --- a/arch/arm64/include/asm/pgtable.h > +++ b/arch/arm64/include/asm/pgtable.h > @@ -451,6 +451,7 @@ static inline pmd_t pmd_mkdevmap(pmd_t pmd) > #define pfn_pmd(pfn,prot) __pmd(__phys_to_pmd_val((phys_addr_t)(pfn) << PAGE_SHIFT) | pgprot_val(prot)) > #define mk_pmd(page,prot) pfn_pmd(page_to_pfn(page),prot) > > +#define pud_dirty(pud) pte_dirty(pud_pte(pud)) > #define pud_young(pud) pte_young(pud_pte(pud)) > #define pud_mkyoung(pud) pte_pud(pte_mkyoung(pud_pte(pud))) > #define pud_write(pud) pte_write(pud_pte(pud)) I think pud_dirty() should only be defined if CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD which is not the case on arm64. Well, the pud_young/mkyoung/write should probably also be removed until we have pud pages on arm64. The wp_clean_pud_entry() function bails out early since pud_trans_unstable() returns 0 on arm64. So we either bracket this function by some #ifdef CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD or we make some generic definitions for pud_* accessors when we don't have this config. -- Catalin