Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4997272imm; Tue, 7 Aug 2018 10:48:38 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfnGw66a4wt3Vn+Eeak+iuPXDr2r0xMvoaYcfm4Yj4aXjpX6vnx6xtTaFoyZ/LPz5tofyKa X-Received: by 2002:a62:864a:: with SMTP id x71-v6mr22981021pfd.252.1533664118222; Tue, 07 Aug 2018 10:48:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533664118; cv=none; d=google.com; s=arc-20160816; b=EYURrK4uflX6C+xwqypAv0DqnzIVLuHvY8NN248ZnI6nwnz+CleBCtAn3B+eyqd9q3 aHLXYSes43hIuUN5jar79BQSAjZhb3xVEY5tDBu0/+gNDGZhENDgx7g+y+N/gY35YhRA xO4kDaOVGmv4Et/iOFxNcVHgLKRDfvyYlsqXq9CvgJBA2fMO4Azja1O+WKJqMqoonyr/ HFYActmTWhDCksaeh3s5oFtEuab9+7jzA/UkrLrZ1h8IrwV99e+6u3WNqQB7kqAnwZGZ 4CyLwSY97iLz4+gP0G+h79DErDRFP/zsH+hrmeBLxBGSbIQVyPNFr/yCwgZr7Q3f+29V Cl9g== 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=pwBH1wVZP+xuXJycolmewFWToMznj2UdaPjRzx7R3XY=; b=IR1cKP83T8mXwTEMvdPZ8+cNX5gHtGXi+KTscm4fSv8j+QJY1DZI1HI0o2ZkMZtx9E y8aTGeuY6t8LNEOgZch9l+TmhF6gDmWEhbNpC6fvmH5LXOvd46MKVNy2Tzxg9HKcPRnc 6jOPKMu5JSQh9nkNXUgKrxWv3TRs1fVBgnP0/UiDXmzN8Pm1LOSCdWmVNq/KmNY3iy7w ObZMb8QzbS3cJ5W3oB9H5tzlmB5z4EA1OIcCb6cI3MIDaD4m3pCgnnnZprn+rIsWdjss WIxgQYWmBmJMh4pvs2vpvooUFTiiTPx2ytU8GA4IR5WQQ7KkGY0tBIrmocbCuTEmyjhO YpxA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p10-v6si1975025pgm.265.2018.08.07.10.48.23; Tue, 07 Aug 2018 10:48:38 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389787AbeHGRNt (ORCPT + 99 others); Tue, 7 Aug 2018 13:13:49 -0400 Received: from mx2.suse.de ([195.135.220.15]:60066 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2389481AbeHGRNs (ORCPT ); Tue, 7 Aug 2018 13:13:48 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 9AEEBAE04; Tue, 7 Aug 2018 14:59:03 +0000 (UTC) Date: Tue, 7 Aug 2018 16:59:00 +0200 From: Michal Hocko To: Jerome Glisse Cc: osalvador@techadventures.net, akpm@linux-foundation.org, dan.j.williams@intel.com, pasha.tatashin@oracle.com, david@redhat.com, yasu.isimatu@gmail.com, logang@deltatee.com, dave.jiang@intel.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Oscar Salvador Subject: Re: [RFC PATCH 2/3] mm/memory_hotplug: Create __shrink_pages and move it to offline_pages Message-ID: <20180807145900.GH10003@dhcp22.suse.cz> References: <20180807133757.18352-1-osalvador@techadventures.net> <20180807133757.18352-3-osalvador@techadventures.net> <20180807135221.GA3301@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180807135221.GA3301@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 07-08-18 09:52:21, Jerome Glisse wrote: > On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalvador@techadventures.net wrote: > > From: Oscar Salvador > > [...] > > > diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c > > index 9bd629944c91..e33555651e46 100644 > > --- a/mm/memory_hotplug.c > > +++ b/mm/memory_hotplug.c > > [...] > > > /** > > * __remove_pages() - remove sections of pages from a zone > > - * @zone: zone from which pages need to be removed > > + * @nid: node which pages belong to > > * @phys_start_pfn: starting pageframe (must be aligned to start of a section) > > * @nr_pages: number of pages to remove (must be multiple of section size) > > * @altmap: alternative device page map or %NULL if default memmap is used > > @@ -548,7 +557,7 @@ static int __remove_section(struct zone *zone, struct mem_section *ms, > > * sure that pages are marked reserved and zones are adjust properly by > > * calling offline_pages(). > > */ > > -int __remove_pages(struct zone *zone, unsigned long phys_start_pfn, > > +int __remove_pages(int nid, unsigned long phys_start_pfn, > > unsigned long nr_pages, struct vmem_altmap *altmap) > > { > > unsigned long i; > > @@ -556,10 +565,9 @@ int __remove_pages(struct zone *zone, unsigned long phys_start_pfn, > > int sections_to_remove, ret = 0; > > > > /* In the ZONE_DEVICE case device driver owns the memory region */ > > - if (is_dev_zone(zone)) { > > - if (altmap) > > - map_offset = vmem_altmap_offset(altmap); > > - } else { > > + if (altmap) > > + map_offset = vmem_altmap_offset(altmap); > > + else { > > This will break ZONE_DEVICE at least for HMM. While i think that > altmap -> ZONE_DEVICE (ie altmap imply ZONE_DEVICE) the reverse > is not true ie ZONE_DEVICE does not necessarily imply altmap. So > with the above changes you change the expected behavior. Could you be more specific what is the expected behavior here? Is this about calling release_mem_region_adjustable? Why does is it not suitable for zone device ranges? -- Michal Hocko SUSE Labs