Received: by 10.213.65.68 with SMTP id h4csp1481010imn; Thu, 15 Mar 2018 00:18:44 -0700 (PDT) X-Google-Smtp-Source: AG47ELsJCHZFl8+oLUxgMkY1Im2K2LtFJ+h4OfUqNy+p9rmCEBAv8s1obPlP/DbNL+C4r0agyIUl X-Received: by 2002:a17:902:227:: with SMTP id 36-v6mr6774901plc.134.1521098324716; Thu, 15 Mar 2018 00:18:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521098324; cv=none; d=google.com; s=arc-20160816; b=mhZpBu93Id6XK3li0SxcNJSgiM41in/BTihE2nyTcVQh6HnBPZ22WxiYaeSOw138x9 qwoPLtlwlE3XLly9BVjBBNBCK32qMgIXXxqj7a7Y1tProUejZJx8cNdxKDVS628/zz+e wUtv/aKQofbD9wUgNA8V0ZmO6johthRl8XavQRm8CO9IC9R7TFa+KZdFkHRj4Zz8bQ9o FOtxY6MgG/8emDCW1qdGOM5G07PeCxN2yw2gZq8Zf2jB0cTfaztAPDLqPLs16wlyqHry Y6FIICfB2zwtFymPITZyHCP96KconkdREakzplgZDQuRChzMI0Y4ReAgA5SzBFm0aJGM 8m6A== 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:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=9jihw+9TlbYnazzvYcZp7JHuTVAB3xKpIQKhIWyWCik=; b=dZWE/Vhq+AIBk6LHpJ2PuLLLO8LzCQus4mgSHGT6Eu1XE9VZoiQZCuX+BRHInPTAZh D/+paXSNkyFkGtwMbXGFo9RGmhPuhjUvcJ7v9crt/S+sl6vOeQeOGCW/IkZOfJAsuiih YYH+0B9IQs8hbFuZ3jHDQGf8RJOUHVFqulNWEHSEE22NecJyXUnm8PHWkRI/DdaqFT9/ omvRwCoPmlbT8W2ZsMMafShF/oTBC5xLN2doieCy7wxKe87KxJnkBwVNAkdkrIFxgo5X gc/f328cSfwLqtSE/Nf0Q3C9o0eVZonvLei/Pc8Wl0pPx6BGsbWhHGgwWKN0fvcThwX5 cuJg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=SeizeR6y; dkim=pass header.i=@codeaurora.org header.s=default header.b=SeizeR6y; 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 g3si3050481pgc.14.2018.03.15.00.18.30; Thu, 15 Mar 2018 00:18:44 -0700 (PDT) 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=@codeaurora.org header.s=default header.b=SeizeR6y; dkim=pass header.i=@codeaurora.org header.s=default header.b=SeizeR6y; 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 S1751571AbeCOHRh (ORCPT + 99 others); Thu, 15 Mar 2018 03:17:37 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:55774 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750715AbeCOHRd (ORCPT ); Thu, 15 Mar 2018 03:17:33 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id EE92260C4F; Thu, 15 Mar 2018 07:17:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1521098252; bh=E33DL+qzRm+E1tuGvHvRqSIyUxjyaapNHJ1c/snvamE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=SeizeR6yPJzcdUvYuaDxgPqZ4VCAERY2e91pfkLcc0LtYlj9NCeDtkKGjnv44NPOZ mNPTdWfoxlw4TvgIqoGDxeQgh08K1BEZ5oiR3hnJgtRiZjQxLwcUeE5W4YrEU3aj7i GpY9gIm4bahPx1S2dwUojHQzRSZptIVyTfgtuz5c= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from [10.204.79.109] (blr-c-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.19.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: cpandya@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 0AD8460590; Thu, 15 Mar 2018 07:17:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1521098252; bh=E33DL+qzRm+E1tuGvHvRqSIyUxjyaapNHJ1c/snvamE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=SeizeR6yPJzcdUvYuaDxgPqZ4VCAERY2e91pfkLcc0LtYlj9NCeDtkKGjnv44NPOZ mNPTdWfoxlw4TvgIqoGDxeQgh08K1BEZ5oiR3hnJgtRiZjQxLwcUeE5W4YrEU3aj7i GpY9gIm4bahPx1S2dwUojHQzRSZptIVyTfgtuz5c= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 0AD8460590 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=cpandya@codeaurora.org Subject: Re: [PATCH v1 0/4] Fix issues with huge mapping in ioremap To: "Kani, Toshi" , "catalin.marinas@arm.com" , "will.deacon@arm.com" , "arnd@arndb.de" Cc: "linux-kernel@vger.kernel.org" , "ard.biesheuvel@linaro.org" , "tglx@linutronix.de" , "takahiro.akashi@linaro.org" , "james.morse@arm.com" , "kristina.martsenko@arm.com" , "mark.rutland@arm.com" , "akpm@linux-foundation.org" , "gregkh@linuxfoundation.org" , "linux-arm-kernel@lists.infradead.org" , "marc.zyngier@arm.com" , "linux-arch@vger.kernel.org" References: <1521017305-28518-1-git-send-email-cpandya@codeaurora.org> <1521038277.2693.131.camel@hpe.com> From: Chintan Pandya Message-ID: <9954bd28-0457-b80e-8af7-6259b63533f2@codeaurora.org> Date: Thu, 15 Mar 2018 12:47:25 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1521038277.2693.131.camel@hpe.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/14/2018 8:08 PM, Kani, Toshi wrote: > On Wed, 2018-03-14 at 14:18 +0530, Chintan Pandya wrote: >> Note: I was working on these patches for quite sometime >> and realized that Toshi Kani has shared some patches >> addressing the same isssue with subject >> "[PATCH 0/2] fix memory leak / panic in ioremap huge pages". >> I've taken slightly different approach here, so sending >> to the list, finally. > > Hi Chintan, Hi Toshi > > Do you have any issue in my patchset? If so, can you please comment on Not functional issues. But I didn't see issues you mentioned in your commit text being solved for ARM64 in your patches. It is just being masked which they were already by Will's patch. In my approach, end goal was to get benefits of huge mapping back for ARM64. > them? It complicates the thing when you send a different approach > without telling why a different approach is needed. Your approach See my reply above. I just had my original patches and I sent it. > purges TLB after updating pmd/pud, which I think is broken. Can you Yes, they are broken. I understood the issues after Mark and Marc's review comments. > work on top of my patchset and properly implement pXd_free_pte_page() I have realized that if I address Mark's comments, my new patch will look similar to what you have done. So, I will work on top of your patches. > for arm64? I will send out my v2 today. > > Thanks, > -Toshi > Chintan -- Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project