Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3429286imm; Mon, 4 Jun 2018 03:33:41 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI8emdxqftrSe2syQ2YG0OWmPtzghBsVgevq/PC39yQm9VcdiBsxFaaUSxc5ek9c5uMSPwa X-Received: by 2002:a65:404d:: with SMTP id h13-v6mr12762035pgp.62.1528108421823; Mon, 04 Jun 2018 03:33:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528108421; cv=none; d=google.com; s=arc-20160816; b=qHOw6KSN8/okHbc7LsmnpASTgctOWxY6hnRpRzsSolUHV5Mxo1OtIGw+x9zTfq/NFw J1xI9sbstUTfB3Dd+OsPy0hicP/xJmdrXtI/TEVhL12S3UILp9z8QXGlJPlYOFu5Pi+J PSQjIbg36H4SR4O/+7zZZ7Cy68oTKGMYBurtjTU/ZEUsKDhEFWINkVS/I2kwu6onc5mO +JAntOP/h6ckZE2DvWQVYE5arJuIigDkhTsMroBJGWHnzzsVls+X216V4igr5PpFJJAd hydXo4mkmi4oALP8MDVhf0mWxWNa/vyNzIt/8l8YQ76lSN4F34sMYIURC++PP9vi0B/T gWYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=Lg6ZYb5H9jh68/e0bK6YDxvG1RMEaaJJag9a1ZQdVWc=; b=TPhm+muM4y6AIHRR3Ld4fALGpDeBViN/rvrxbqUMOKRLbEge9vgMGyXwvu9VZN/KrS CM7vOzUENPJzzQsw56d/eatn7o+BdiwtIwHfe31ycqP1a34BzJTpvCNLPr7Ad/pJIewy /7+A0RyEYS03uxEOLBHAd+YncV/R8gYHvws7PZMJx/VBBhRJR0CnogYyZVpCFdjpC5AV 30OA4zKGfqHgOTOr6dmCxSNlmH5JSavWW6QYMCXaXkIjt7AnGDOO2Lq7sGtBylkb6MVx 4ynzNhK1kFGemSpJRqKDVWvO6MsLg25dMT6rA8hCbf7rrX/hRrmjBe/YM8zo9cf9Z8Kn EiKg== ARC-Authentication-Results: i=1; mx.google.com; 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 n3-v6si45169594pld.116.2018.06.04.03.33.27; Mon, 04 Jun 2018 03:33:41 -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; 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 S1751798AbeFDKdC (ORCPT + 99 others); Mon, 4 Jun 2018 06:33:02 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:41362 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750868AbeFDKdB (ORCPT ); Mon, 4 Jun 2018 06:33:01 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 87D8D1435; Mon, 4 Jun 2018 03:33:01 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 58AF23F557; Mon, 4 Jun 2018 03:33:01 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id B03021AE0FA1; Mon, 4 Jun 2018 11:33:32 +0100 (BST) Date: Mon, 4 Jun 2018 11:33:32 +0100 From: Will Deacon To: Chintan Pandya Cc: catalin.marinas@arm.com, mark.rutland@arm.com, akpm@linux-foundation.org, toshi.kani@hpe.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v12 0/5] Fix issues with huge mapping in ioremap for ARM64 Message-ID: <20180604103332.GF9482@arm.com> References: <1527856758-27169-1-git-send-email-cpandya@codeaurora.org> <1a648674-da56-6664-bf3c-0cdf825ad1e3@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1a648674-da56-6664-bf3c-0cdf825ad1e3@codeaurora.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Chintan, On Mon, Jun 04, 2018 at 11:26:28AM +0530, Chintan Pandya wrote: > Just curious to know, is there anything that I should be addressing > in these patches ? For now, I don't see anything from my side that > requires modification, unless one has some more review comments on > this. > > Status so far on and around this: > - Status of Toshi's series of patches is still not clear to me. > However, if this series can get through first, there won't > be conflicting scenarios as far as arm64 is concerned. > - I've rebased these patches on tip > - Also re-tested these patches for long duration tests with > 1 GB mapping case also exercised enough. Test ended positively. I'll try to review this version today. Will