From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: ebiederm@xmission.com (Eric W. Biederman) References: <34274b02-60ba-eb78-eacd-6dc1146ed3cd@arm.com> <80e4d1d7-f493-3f66-f700-86f18002d692@redhat.com> <20200410121013.03b609fd572504c03a666f4a@linux-foundation.org> <20200411034414.GH2129@MiWiFi-R3L-srv> <20200411093009.GH25745@shell.armlinux.org.uk> <20200412053507.GA4247@MiWiFi-R3L-srv> <20200412080836.GM25745@shell.armlinux.org.uk> <87wo6klbw0.fsf@x220.int.ebiederm.org> <20200413023701.GA20265@MiWiFi-R3L-srv> <871rorjzmc.fsf@x220.int.ebiederm.org> <20200413160144.0e07c0033afc474228bc9218@linux-foundation.org> Date: Tue, 14 Apr 2020 01:13:25 -0500 In-Reply-To: <20200413160144.0e07c0033afc474228bc9218@linux-foundation.org> (Andrew Morton's message of "Mon, 13 Apr 2020 16:01:44 -0700") Message-ID: <87tv1miohm.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Subject: Re: [PATCH 1/3] kexec: Prevent removal of memory in use by a loaded kexec image List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Andrew Morton Cc: Baoquan He , David Hildenbrand , Catalin Marinas , Bhupesh Sharma , Anshuman Khandual , kexec@lists.infradead.org, Russell King - ARM Linux admin , linux-mm@kvack.org, James Morse , Will Deacon , linux-arm-kernel@lists.infradead.org Andrew Morton writes: > On Mon, 13 Apr 2020 08:15:23 -0500 ebiederm@xmission.com (Eric W. Biederman) wrote: > >> > For 3), people can still use kexec_load and develop/fix for it, if no >> > kexec_file_load supported. But 32-bit arm should be a different one, >> > more like i386, we will leave it as is, and fix anything which could >> > break it. But people really expects to improve or add feature to it? E.g >> > in this patchset, the mem hotplug issue James raised, I assume James is >> > focusing on arm64, x86_64, but not 32-bit arm. As DavidH commented in >> > another reply, people even don't agree to continue supporting memory >> > hotplug on 32-bit system. We ever took effort to fix a memory hotplug >> > bug on i386 with a patch, but people would rather set it as BROKEN. >> >> For memory hotplug just reload. Userspace already gets good events. >> >> We should not expect anything except a panic kernel to be loaded over a >> memory hotplug event. The kexec on panic code should actually be loaded >> in a location that we don't reliquish if asked for it. > > Is that a nack for James's patchset? I have just read the end of the thread and I have the sense that the patchset had already been rejected. I will see if I can go back and read the beginning. I was mostly reacting to the idea that you could stop maintaining an interface that people are actively using because there is a newer interface. Eric _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec