[lkml]   [2019]   [Feb]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr
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?!


Good mailing practices for 400: avoid top-posting and trim the reply.

 \ /
  Last update: 2019-02-15 11:25    [W:0.144 / U:2.720 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site