From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45774C433EF for ; Mon, 21 Mar 2022 15:24:14 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B608F6B0072; Mon, 21 Mar 2022 11:24:13 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B10646B0073; Mon, 21 Mar 2022 11:24:13 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 98A9F8D0001; Mon, 21 Mar 2022 11:24:13 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.27]) by kanga.kvack.org (Postfix) with ESMTP id 858B06B0072 for ; Mon, 21 Mar 2022 11:24:13 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay13.hostedemail.com (Postfix) with ESMTP id 606F9610E5 for ; Mon, 21 Mar 2022 15:24:13 +0000 (UTC) X-FDA: 79268764386.11.3AE5239 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf07.hostedemail.com (Postfix) with ESMTP id CEB5C4001E for ; Mon, 21 Mar 2022 15:24:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647876252; 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: in-reply-to:in-reply-to:references:references; bh=gkwfmV9h90rKkg7JIWAtJfnSFaMHQkfhf23YAP5P8Rg=; b=ZAPxojj9L6+BgXIs60HJzLGS5xCMABz4uBOmHpIj1xpWHIw4le10KUTtk92BWDhnGUBRbT 894RnDsR2b7N2pxZ68Ni0yoUTidrC2TrV1MuS8rfbn2V/Fsu/Y45+j0RcU9Ep7+jgt1tG+ URObtAyKsG+JpIwwAUH0YQdlTN38F1A= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-316-waAWePpROpaHR8JAmzMzhA-1; Mon, 21 Mar 2022 11:24:11 -0400 X-MC-Unique: waAWePpROpaHR8JAmzMzhA-1 Received: by mail-wm1-f71.google.com with SMTP id i65-20020a1c3b44000000b00385c3f3defaso4221349wma.3 for ; Mon, 21 Mar 2022 08:24:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:cc:references:organization:in-reply-to :content-transfer-encoding; bh=gkwfmV9h90rKkg7JIWAtJfnSFaMHQkfhf23YAP5P8Rg=; b=k+EKEySPbM1norWdhOEHHwir3f/Ce9IOvuV487j1eih1GDC1xSPYN9zGRRs5bYOp9z vn/ousDRq8lh6q/dhYZI4QMbJJXKLYBm5/ANzJLMvkwiE65mpFynkZdsVp1F+cGj1y/s FnhmfSMfyrB1Cm/XQqvOeemG+GJeS/e9hFR47hDCtf6ptgyjXNpVSfGFiJSe9K2ilxQT piBW0pcbzimBff9FQlRH7eYmlu4JZHWwCwJuCjg3jRFIGTSrmw3Zl6wxZqY0dF+YdHzo +ybBkmGIS7HZQic2v0ugBcCBxMfB6foJOtf+nte730KNfh9jDc+o02RLMoZg4Y9vIF2o sFhw== X-Gm-Message-State: AOAM53214oVZOK2SpxwTwYjL5gnQ9vTWl4BEVKxWSg1Hgn2AONrYHbGI IMwy0gRmuE3XM5Ij0nhrMBqrZ6v4cUMkaOOhCTCthyfbVXVB87McY+CAOW0xde5KirdXiM6FOZx UUzi9lOvXC8U= X-Received: by 2002:a05:600c:3c8a:b0:389:cf43:eaf6 with SMTP id bg10-20020a05600c3c8a00b00389cf43eaf6mr19810857wmb.199.1647876249782; Mon, 21 Mar 2022 08:24:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwegmlA7v6h+7OLrqTmDae/ZCWlQDUWC84R+Dmzz23xCWP1ygvd+1BcbP8JTZ0/E58v29s+ZQ== X-Received: by 2002:a05:600c:3c8a:b0:389:cf43:eaf6 with SMTP id bg10-20020a05600c3c8a00b00389cf43eaf6mr19810829wmb.199.1647876249539; Mon, 21 Mar 2022 08:24:09 -0700 (PDT) Received: from ?IPV6:2003:cb:c704:4900:849b:f76e:5e1f:ff95? (p200300cbc7044900849bf76e5e1fff95.dip0.t-ipconnect.de. [2003:cb:c704:4900:849b:f76e:5e1f:ff95]) by smtp.gmail.com with ESMTPSA id f13-20020a05600c4e8d00b0038c949ef0d5sm7269674wmq.8.2022.03.21.08.24.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Mar 2022 08:24:09 -0700 (PDT) Message-ID: Date: Mon, 21 Mar 2022 16:24:08 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2 Subject: Re: [GIT PULL] Folio patches for 5.18 (MM part) From: David Hildenbrand To: Matthew Wilcox , Linus Torvalds Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Christoph Hellwig , Hugh Dickins , Alex Sierra , Alistair Popple , Miaohe Lin , Mike Rapoport , William Kucharski References: <9ae0a8e4-41b7-04f4-4435-17cbba9850fb@redhat.com> Organization: Red Hat In-Reply-To: <9ae0a8e4-41b7-04f4-4435-17cbba9850fb@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: CEB5C4001E X-Rspam-User: Authentication-Results: imf07.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=ZAPxojj9; spf=none (imf07.hostedemail.com: domain of david@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=david@redhat.com; dmarc=pass (policy=none) header.from=redhat.com X-Stat-Signature: an3np5ox1xxursa5wqdcrdp5aaipch4g X-Rspamd-Server: rspam07 X-HE-Tag: 1647876252-957794 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 21.03.22 16:16, David Hildenbrand wrote: > On 21.03.22 14:30, Matthew Wilcox wrote: >> Hi Linus, >> >> This is the first of two folio-related pull requests for this merge >> window. This is the MM side of things and we had some unfortunate >> complex merge conflicts to resolve. I decided to redo my changes on >> top of Hugh's and Christoph's patches, so I'm the one sending the >> pull request. >> >> The following changes since commit f71077a4d84bbe8c7b91b7db7c4ef815755ac5e3: >> >> Merge tag 'mmc-v5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc (2022-02-16 12:09:22 -0800) >> >> are available in the Git repository at: >> >> git://git.infradead.org/users/willy/pagecache.git tags/folio-5.18 >> >> for you to fetch changes up to 5063f22c914e3e5f2239cf91f4986042dc705bde: >> >> mm/damon: minor cleanup for damon_pa_young (2022-03-16 10:09:50 -0400) >> >> ---------------------------------------------------------------- >> Folio changes for 5.18 >> >> Several of us had overlapping, conflicting changes to the MM this >> round, and I volunteered to send the pull request. >> >> - Hugh rewrote how munlock works to massively reduce the contention >> on i_mmap_rwsem: >> https://lore.kernel.org/linux-mm/8e4356d-9622-a7f0-b2c-f116b5f2efea@google.com/ >> - Christoph sorted out the page refcount mess for ZONE_DEVICE pages: >> https://lore.kernel.org/linux-mm/20220210072828.2930359-1-hch@lst.de/ >> - I converted GUP to use folios and make pincount available for order-1 >> pages. >> - I converted a few more truncation functions to use folios >> - I converted page_vma_mapped_walk to use PFNs instead of pages >> - I converted rmap_walk to use folios >> - I converted most of shrink_page_list() to use a folio >> - I added support for creating large folios in readahead >> >> ---------------------------------------------------------------- >> Alex Sierra (10): >> mm: add zone device coherent type memory support >> mm: add device coherent vma selection for memory migration >> mm/gup: fail get_user_pages for LONGTERM dev coherent type >> drm/amdkfd: add SPM support for SVM >> drm/amdkfd: coherent type as sys mem on migration to ram >> lib: test_hmm add ioctl to get zone device type >> lib: test_hmm add module param for zone device type >> lib: add support for device coherent type in test_hmm >> tools: update hmm-test to support device coherent type >> tools: update test_hmm script to support SP config >> >> Alistair Popple (2): >> mm: remove the vma check in migrate_vma_setup() >> mm/gup: migrate device coherent pages when pinning instead of failing > > ... I thought DEVICE_COHERENT is still under development? > After verifying that I'm not daydreaming [1] (and realizing that I had review comments to some of these patches that have not been resolved yet) and also not spotting these change in your changelog above, I assume this stuff was included by mistake. NACK to merging DEVICE_COHERENT at this point. [1] https://lkml.kernel.org/r/20220310172633.9151-1-alex.sierra@amd.com -- Thanks, David / dhildenb