Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp841534ybd; Wed, 26 Jun 2019 06:55:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqy2m41BYJUJGPhkaDvukXqN/OVBcu9RfGMhECmdnXD0tpC49bNgsOjcIWBV1djXkWtIQ8aU X-Received: by 2002:a17:902:b187:: with SMTP id s7mr5540350plr.309.1561557326169; Wed, 26 Jun 2019 06:55:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561557326; cv=none; d=google.com; s=arc-20160816; b=iX/40Umd+cvaiT1Vxdi4K896hzsb6VAxceJPnJXARHzlaL76cEtj1bGuLrfDZmpOYC U2ITyjArtFGSIFlRwiiueX6Ki7E+KQnVsxGT39rqxqAomD7UKjBZFXvy87JN0m4iT0IZ B9LUiTlpJVwdM2CZlsjYQd7x7TBtCFCaECaJYuYlDdmIlIoZ5jJPUVWKKDzNWWcS6hNp VjpuclIxHt/C2BNsBVE7NcAAZ64KI8ziLQ4sSgGhZPA5Jbk4fPNW2cw9MJ1COWslqrvj ARf0FkJQzHONknetobLW+1S5NT963uc/l45vpfXsB7D2H8akl4WmhV4WMAoYZmiMSMYJ F/hQ== 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; bh=xXr3uz6EvKpjzSrBgtJXu2l135EJdGIcBr08dZAq+Fw=; b=tYxJchlb0cD1Tr+PbQEk25Zu3nkK+7f1XP7qNUXqQWeHw00rIQhRBuZdJNyoRb/yyT MUH05DpKWcP0C3kmOePdZczOMUox1PQMHDBPVyA4u8e2UsbLz8l6mh6OfUoV7gAhEYAe +r5N2tBr7C3c9Pfoftt3gG5NXLiZ1Du3gw0OS/Sk/DLJkZXmsVMpQrzsJIVeH7SMRASv hMU4H7qKSUQ7SClQhGYiHDlN2iM/9/hI1WZ8kdyDgHiuRZ/uw4/TSnZqfR9+n04Nhahu LbpP0uheC/Hw3QTcu5/oARd+pzfNA8OtFtcICURzPvNBK/ySyWURrL0i+XjXH/RN5z2s eXdA== 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 f17si16135626pgv.338.2019.06.26.06.55.09; Wed, 26 Jun 2019 06:55:26 -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 S1727872AbfFZNyz (ORCPT + 99 others); Wed, 26 Jun 2019 09:54:55 -0400 Received: from mx2.suse.de ([195.135.220.15]:48626 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727750AbfFZNyy (ORCPT ); Wed, 26 Jun 2019 09:54:54 -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 D2ABDAE3F; Wed, 26 Jun 2019 13:54:52 +0000 (UTC) Date: Wed, 26 Jun 2019 15:54:50 +0200 From: Michal Hocko To: Barret Rhoden Cc: linux-mm@kvack.org, Pingfan Liu , Dave Hansen , Peter Zijlstra , x86@kernel.org, Benjamin Herrenschmidt , Michael Ellerman , Tony Luck , linuxppc-dev@lists.ozlabs.org, linux-ia64@vger.kernel.org, LKML , Ingo Molnar Subject: Re: [PATCH 1/2] x86, numa: always initialize all possible nodes Message-ID: <20190626135450.GW17798@dhcp22.suse.cz> References: <20190212095343.23315-1-mhocko@kernel.org> <20190212095343.23315-2-mhocko@kernel.org> <34f96661-41c2-27cc-422d-5a7aab526f87@google.com> <20190502130031.GC29835@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190502130031.GC29835@dhcp22.suse.cz> 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 Thu 02-05-19 09:00:31, Michal Hocko wrote: > On Wed 01-05-19 15:12:32, Barret Rhoden wrote: > [...] > > A more elegant solution may be to avoid registering with sysfs during early > > boot, or something else entirely. But I figured I'd ask for help at this > > point. =) > > Thanks for the report and an excellent analysis! This is really helpful. > I will think about this some more but I am traveling this week. It seems > really awkward to register a sysfs file for an empty range. That looks > like a bug to me. I am sorry, but I didn't get to this for a long time and I am still busy. The patch has been dropped from the mm tree (thus linux-next). I hope I can revisit this or somebody else will take over and finish this work. This is much more trickier than I anticipated unfortunately. -- Michal Hocko SUSE Labs