Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp7407069ybh; Thu, 8 Aug 2019 15:22:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqwc49yi09epP0yojlutNw6z66DXK+XpuE0ZkdSQHhec6kn8SmoaTu9FynAE9fMO/bX+Vdek X-Received: by 2002:a63:6f8f:: with SMTP id k137mr14662584pgc.90.1565302947695; Thu, 08 Aug 2019 15:22:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565302947; cv=none; d=google.com; s=arc-20160816; b=HOYVxKiOrEJZMjswEcasB+M7V8SQAvREJ2V4/D5BI6ZWuFzZyjEwzFOBbsBSPV2q+W wmGnZnQIO2KzLZOZhECabXSdMoiyXxlWbN5dGRwoHD2bheH3FwQPJ0nNovRGLDk1BVNX rGumk8Bvp7vc4fD0/VXIPiIt4v5e0TCPVEAna7VnnpYwa0fUq6ISLLd/sDpQPmLfVSji viZLL/JIki9B+J/tZyeSkTiLMwY08k1P/QxccVKvCYAUjXaR+xBgpPGLDO+yej/0Wn3e Z7OEApxUxfdQNinGA4loVNIOu2lrWK9yp4gY4h9F6JUlf2fdsFYYaD7MTE0itwUWj/Rw 0gmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=A+owftgg6ciRMxMAA6PqstMhK9e//nAGDN3c1g//Qyw=; b=SrwiwszR1/yhF757pAen4w3XNYpmyktiLaTCiTl/Yhc153O6hUPwYUPXAAdNKLhsfM re+d7REI/fMX44CKcncWaGvHYSkZJiu+RyX1ur88BbtjxG+/MgZPMJwgw8F6qMF3Q09Y oK7xgX6U+UZQmbPIcmn+nO6KG9tGPVlQM9AmCi0MAKPtY9ODzI9q6B9lme/roii85CgT lGY48wa35aJMbDfIOQKzRXGpfk6QsTmuyZP7D+jJ/6//GMDRKQg5ytJDUKmwgLs1lWPZ +5AoSuqo7EDwLMOYJZcUFSu5vATEDo/FnVl3lP8zcjmx9XKUUmCabgCwZkC9PctWWHSN ZWIA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=Js30zXpc; 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 w19si44387865pga.462.2019.08.08.15.22.12; Thu, 08 Aug 2019 15:22:27 -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=fail (test mode) header.i=@shipmail.org header.s=mail header.b=Js30zXpc; 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 S2404622AbfHHWVa (ORCPT + 99 others); Thu, 8 Aug 2019 18:21:30 -0400 Received: from pio-pvt-msa1.bahnhof.se ([79.136.2.40]:49724 "EHLO pio-pvt-msa1.bahnhof.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404589AbfHHWVa (ORCPT ); Thu, 8 Aug 2019 18:21:30 -0400 Received: from localhost (localhost [127.0.0.1]) by pio-pvt-msa1.bahnhof.se (Postfix) with ESMTP id C00AF3F3CA; Fri, 9 Aug 2019 00:21:27 +0200 (CEST) Authentication-Results: pio-pvt-msa1.bahnhof.se; dkim=pass (1024-bit key; unprotected) header.d=shipmail.org header.i=@shipmail.org header.b="Js30zXpc"; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at bahnhof.se X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=6.31 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from pio-pvt-msa1.bahnhof.se ([127.0.0.1]) by localhost (pio-pvt-msa1.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aL-YyBR6tXjE; Fri, 9 Aug 2019 00:21:26 +0200 (CEST) Received: from mail1.shipmail.org (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) (Authenticated sender: mb878879) by pio-pvt-msa1.bahnhof.se (Postfix) with ESMTPA id CD18A3F398; Fri, 9 Aug 2019 00:21:25 +0200 (CEST) Received: from localhost.localdomain (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) by mail1.shipmail.org (Postfix) with ESMTPSA id 16C1136015E; Fri, 9 Aug 2019 00:21:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=shipmail.org; s=mail; t=1565302885; bh=RVaCu1C5tAq3VjSBjXkZ1UBuhKLiLy/Tpb94K/nrtEA=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Js30zXpcy30+ZBx1NEVIkzvBdlmXRihLBZvVid2tt64zg/qVBCw5XIppSy+A4/doJ S/Q+ly9RkbBXM53IERB8Qzr0uGGHeOvMLz8hKp5L7qJTDmfveaf3yO1s/0j0tOGStZ 5qDimRq6xCm3+fuzaPD+XJtHGufRdRJ3+QCW7L9g= Subject: Re: cleanup the walk_page_range interface To: Christoph Hellwig , Linus Torvalds Cc: Andrew Morton , Jerome Glisse , Jason Gunthorpe , Steven Price , Linux-MM , Linux List Kernel Mailing References: <20190808154240.9384-1-hch@lst.de> <20190808215632.GA12773@lst.de> From: Thomas Hellstrom Message-ID: Date: Fri, 9 Aug 2019 00:21:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190808215632.GA12773@lst.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/8/19 11:56 PM, Christoph Hellwig wrote: > On Thu, Aug 08, 2019 at 10:50:37AM -0700, Linus Torvalds wrote: >>> Note that both Thomas and Steven have series touching this area pending, >>> and there are a couple consumer in flux too - the hmm tree already >>> conflicts with this series, and I have potential dma changes on top of >>> the consumers in Thomas and Steven's series, so we'll probably need a >>> git tree similar to the hmm one to synchronize these updates. >> I'd be willing to just merge this now, if that helps. The conversion >> is mechanical, and my only slight worry would be that at least for my >> original patch I didn't build-test the (few) non-x86 >> architecture-specific cases. But I did end up looking at them fairly >> closely (basically using some grep/sed scripts to see that the >> conversions I did matched the same patterns). And your changes look >> like obvious improvements too where any mistake would have been caught >> by the compiler. > I did cross compile the s390 and powerpc bits, but I do not have an > openrisc compiler. > >> So I'm not all that worried from a functionality standpoint, and if >> this will help the next merge window, I'll happily pull now. > That would help with this series vs the others, but not with the other > series vs each other. Although my series doesn't touch the pagewalk code, it rather borrowed some concepts from it and used for the apply_to_page_range() interface. The reason being that the pagewalk code requires the mmap_sem to be held (mainly for trans-huge pages and reading the vma->vm_flags if I understand the code correctly). That is fine when you scan the vmas of a process, but the helpers I wrote need to instead scan all vmas pointing into a struct address_space, and taking the mmap_sem for each vma will create lock inversion problems. /Thomas