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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1AB6DC6369E for ; Thu, 3 Dec 2020 00:12:53 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 3A6C621527 for ; Thu, 3 Dec 2020 00:12:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3A6C621527 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 661966B005C; Wed, 2 Dec 2020 19:12:51 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 612B26B005D; Wed, 2 Dec 2020 19:12:51 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4D9216B0068; Wed, 2 Dec 2020 19:12:51 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0038.hostedemail.com [216.40.44.38]) by kanga.kvack.org (Postfix) with ESMTP id 3886C6B005C for ; Wed, 2 Dec 2020 19:12:51 -0500 (EST) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id F201B3633 for ; Thu, 3 Dec 2020 00:12:50 +0000 (UTC) X-FDA: 77550045300.22.cats26_430d00e273b7 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin22.hostedemail.com (Postfix) with ESMTP id D43DD18038E67 for ; Thu, 3 Dec 2020 00:12:50 +0000 (UTC) X-HE-Tag: cats26_430d00e273b7 X-Filterd-Recvd-Size: 4306 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by imf27.hostedemail.com (Postfix) with ESMTP for ; Thu, 3 Dec 2020 00:12:50 +0000 (UTC) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 39101113E; Wed, 2 Dec 2020 16:12:49 -0800 (PST) Received: from [192.168.0.130] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 95B713F575; Wed, 2 Dec 2020 16:12:45 -0800 (PST) Subject: Re: [RFC V2 0/3] mm/hotplug: Pre-validate the address range with platform To: Heiko Carstens Cc: linux-mm@kvack.org, akpm@linux-foundation.org, david@redhat.com, linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, Vasily Gorbik , Catalin Marinas , Will Deacon , Ard Biesheuvel , Mark Rutland References: <1606706992-26656-1-git-send-email-anshuman.khandual@arm.com> <20201202203540.GC11274@osiris> From: Anshuman Khandual Message-ID: <2d2a947f-3c4f-6106-583a-7da4e757a7aa@arm.com> Date: Thu, 3 Dec 2020 05:42:35 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201202203540.GC11274@osiris> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 12/3/20 2:05 AM, Heiko Carstens wrote: > On Mon, Nov 30, 2020 at 08:59:49AM +0530, Anshuman Khandual wrote: >> This series adds a mechanism allowing platforms to weigh in and prevalidate >> incoming address range before proceeding further with the memory hotplug. >> This helps prevent potential platform errors for the given address range, >> down the hotplug call chain, which inevitably fails the hotplug itself. >> >> This mechanism was suggested by David Hildenbrand during another discussion >> with respect to a memory hotplug fix on arm64 platform. >> >> https://lore.kernel.org/linux-arm-kernel/1600332402-30123-1-git-send-email-anshuman.khandual@arm.com/ >> >> This mechanism focuses on the addressibility aspect and not [sub] section >> alignment aspect. Hence check_hotplug_memory_range() and check_pfn_span() >> have been left unchanged. Wondering if all these can still be unified in >> an expanded memhp_range_allowed() check, that can be called from multiple >> memory hot add and remove paths. >> >> This series applies on v5.10-rc6 and has been slightly tested on arm64. >> But looking for some early feedback here. >> >> Changes in RFC V2: >> >> Incorporated all review feedbacks from David. >> >> - Added additional range check in __segment_load() on s390 which was lost >> - Changed is_private init in pagemap_range() >> - Moved the framework into mm/memory_hotplug.c >> - Made arch_get_addressable_range() a __weak function >> - Renamed arch_get_addressable_range() as arch_get_mappable_range() >> - Callback arch_get_mappable_range() only handles range requiring linear mapping >> - Merged multiple memhp_range_allowed() checks in register_memory_resource() >> - Replaced WARN() with pr_warn() in memhp_range_allowed() >> - Replaced error return code ERANGE with E2BIG >> >> Changes in RFC V1: >> >> https://lore.kernel.org/linux-mm/1606098529-7907-1-git-send-email-anshuman.khandual@arm.com/ >> >> Cc: Heiko Carstens >> Cc: Vasily Gorbik >> Cc: Catalin Marinas >> Cc: Will Deacon >> Cc: Ard Biesheuvel >> Cc: Mark Rutland >> Cc: David Hildenbrand >> Cc: Andrew Morton >> Cc: linux-arm-kernel@lists.infradead.org >> Cc: linux-s390@vger.kernel.org >> Cc: linux-mm@kvack.org >> Cc: linux-kernel@vger.kernel.org > > Btw. please use git send-email's --cc-cover option to make sure that > all patches of this series will be sent to all listed cc's. > I really dislike to receive only the cover-letter and maybe on patch > and then have to figure out where to find the rest. Okay, will ensure that. > > Thanks :) >