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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4B00BCA6017 for ; Sat, 10 Oct 2026 09:42:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:References:Message-Id:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=OwK3cYPVrNJioq6cDGUciBZ4J6LIQhVZQtwNjb9VoI4=; b=MBogxvDzvK4Dcr nvj/qXuGJDegbrJw2nr0HlYKbcVrWRhWyxHbFjxv4hOiwzlnCmkyI+r2yP69noL9G98vtnH/7OX8o AzB+ML1Fkr9qtoOAKTjJw99C/IaY/fpOvEniJyREzga4tEVxA6Mh7wvdsZoITz/ThPkB4KA5xvnoU phgr8DHoQW4RpR4GWoD77+dE0wadxGdS4h2N6Muy0Z0yO4mFq3TcWai95GidAqxGGYhI6a52HTqF3 8O8mXj7bW6MnS7m/0kXR5hxGtGolso4RiFuwUEQZO1s9waxqoldtic/H8Q/vRDsD9fB7gZ5+/jLz1 h5eflG/oiOEMQ44esKEg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xFTbE-00000007nHe-1SSr; Sat, 10 Oct 2026 09:42:40 +0000 Received: from out-249.mta0.migadu.com ([2001:41d0:1004:224b::f9] helo=mta0.migadu.com) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xFTbA-00000007nGq-43fp for linux-riscv@lists.infradead.org; Sat, 10 Oct 2026 09:42:38 +0000 X-Envelope-To: linux-riscv@lists.infradead.org DKIM-Signature: a=rsa-sha256; bh=AYKq4I4pt+XRaSTHkcogaEaoukmbVRkhJcniZ//zAgg=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1791625355; v=1; x=1792230155; b=GkHp9HYwYhlAfeZazSdWeQJrN0BWOreotNM+3ynVXJ6yGnjdQ2Yu157g2bWLcwgamVXkbA93 qVTxIRGoZu3xUgv3nCKemIeKJWgUI7gLXasWnweZklqS1PpbQmM0g6iIdshtoRXyUsOG3ecPmHy UyKbqa5ut/uLpAJg0pbhzZew= X-Envelope-To: linux-riscv@lists.infradead.org Received: by smtp.migadu.com with ESMTPS id 57f0757703d8e229; Sat, 10 Oct 2026 09:42:34 +0000 X-Mizu-Trace-ID: 57f0757703d8e229 X-Migadu-Flow: FLOW_OUT Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.100.1.1.12\)) Subject: Re: [PATCH 0/4] mm: Fix page-table teardown during memory hot-remove From: Muchun Song In-Reply-To: Date: Sat, 10 Oct 2026 17:42:18 +0800 Cc: Muchun Song , akpm@linux-foundation.org, linux-mm@kvack.org, stable@vger.kernel.org, david@kernel.org, osalvador@suse.de, dave.hansen@linux.intel.com, luto@kernel.org, peterz@infradead.org, tglx@kernel.org, mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com, catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr, linux-riscv@lists.infradead.org, agordeev@linux.ibm.com, kevin.brodsky@arm.com, bjorn@rivosinc.com, apopple@nvidia.com, linux-kernel@vger.kernel.org Message-Id: References: <20261008073021.2512665-1-songmuchun@bytedance.com> To: Dave Hansen X-Mailer: Apple Mail (2.3901.100.1.1.12) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20261010_024237_230271_0D4E4612 X-CRM114-Status: GOOD ( 10.34 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org > On Oct 10, 2026, at 04:48, Dave Hansen wrote: > > On 10/8/26 00:30, Muchun Song wrote: >> This series is limited to bug fixes for the existing teardown paths. > > Why is this a series? Why not send the architectures independently? Is > there some dependency where they all need to be applied at once? What do > you want done with this series? Are you expecting it to be merged via > the mm path or the individual arch maintainers? You're right that there is no strict dependency across all three architectures in v1. I grouped them because they address the same page-table constructor/destructor imbalance exposed during memory hot-remove, but that alone does not require them to be applied as one series. For v2, I will move the common destructor handling into pagetable_free() as suggested by David. The RISC-V and arm64 fixes will then depend on that common MM change, so I plan to keep them in one series and have it go through the MM tree, with review or acks from the relevant architecture maintainers. Thanks, Muchun _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv