Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Message-ID: <08e9855c-395d-f40c-de3d-1ec8b644bfe8@redhat.com>
Date:   Tue, 3 May 2022 03:15:24 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.0
Subject: Re: [PATCH] mm: fix is_pinnable_page against on cma page
Content-Language: en-US
To:     Minchan Kim <minchan@kernel.org>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        linux-mm <linux-mm@kvack.org>,
        LKML <linux-kernel@vger.kernel.org>,
        John Hubbard <jhubbard@nvidia.com>,
        John Dias <joaodias@google.com>
References: <20220502173558.2510641-1-minchan@kernel.org>
 <29d0c1c3-a44e-4573-7e7e-32be07544dbe@redhat.com>
 <YnAhaRNjmIhtGUjk@google.com>
From:   David Hildenbrand <david@redhat.com>
Organization: Red Hat
In-Reply-To: <YnAhaRNjmIhtGUjk@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk


>>>> However, I assume we have the same issue right now already with
>> ZONE_MOVABLE and MIGRATE_CMA when trying to pin a page residing on these
> 
> ZONE_MOVALBE is also changed dynamically?
> 

Sorry, with "same issue" I meant failing to pin if having to migrate and
the page is temporarily unmovable.

>> there are temporarily unmovable and we fail to migrate. But it would now
>> apply even without ZONE_MOVABLE or MIGRATE_CMA. Hm...
> 
> Didn't parse your last mention.

On a system that neither uses ZONE_MOVABLE nor MIGRATE_CMA we might have
to migrate now when pinning.

-- 
Thanks,

David / dhildenb