From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.skyhub.de ([2a01:4f8:190:11c2::b:1457]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1guagB-0003ze-DT for kexec@lists.infradead.org; Fri, 15 Feb 2019 10:25:13 +0000 Date: Fri, 15 Feb 2019 11:24:58 +0100 From: Borislav Petkov Subject: Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr Message-ID: <20190215102458.GD10433@zn.tnic> References: <20190125134518.GA23595@dhcp-128-65.nay.redhat.com> <20190125140823.GC27998@zn.tnic> <20190131075907.GB19091@dhcp-128-65.nay.redhat.com> <20190131105732.GC6749@zn.tnic> <20190131222732.GA946@anatevka> <20190131234740.GO6749@zn.tnic> <20190204223016.GB11986@anatevka> <20190205081552.GG21801@zn.tnic> <20190206120804.GC10062@dhcp-128-65.nay.redhat.com> <20190211204816.GB21473@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190211204816.GB21473@dhcp-128-65.nay.redhat.com> 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: Dave Young Cc: Randy Dunlap , bhe@redhat.com, x86@kernel.org, kexec@lists.infradead.org, Jerry Hoemann , Pingfan Liu , linux-kernel@vger.kernel.org, Mike Rapoport , Andrew Morton , yinghai@kernel.org, vgoyal@redhat.com On Tue, Feb 12, 2019 at 04:48:16AM +0800, Dave Young wrote: > Even we make it automatic in kernel, but we have to have some default > value for swiotlb in case crashkernel can not find a free region under 4G. > So this default value can not work for every use cases, people need > manually use crashkernel=,low and crashkernel=,high in case > crashkernel=X does not work. Why would the user need to find swiotlb range? The kernel has all the information it requires at its finger tips in order to decide properly. The user wants a crashkernel range, the kernel tries the low range => no workie, then it tries the next range => workie but needs to allocate swiotlb range so that DMA can happen too. Doh, then the kernel does allocate that too. Why would the user need to do anything here?! -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec