lkml.org 
[lkml]   [2019]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v5 4/4] kdump: update Documentation about crashkernel on arm64
    Date
    Now we support crashkernel=X,[high,low] on arm64, update the
    Documentation.

    Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
    ---
    Documentation/admin-guide/kernel-parameters.txt | 4 ++--
    1 file changed, 2 insertions(+), 2 deletions(-)

    diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
    index 308af3b..a055983 100644
    --- a/Documentation/admin-guide/kernel-parameters.txt
    +++ b/Documentation/admin-guide/kernel-parameters.txt
    @@ -715,14 +715,14 @@
    Documentation/kdump/kdump.txt for an example.

    crashkernel=size[KMG],high
    - [KNL, x86_64] range could be above 4G. Allow kernel
    + [KNL, x86_64, arm64] range could be above 4G. Allow kernel
    to allocate physical memory region from top, so could
    be above 4G if system have more than 4G ram installed.
    Otherwise memory region will be allocated below 4G, if
    available.
    It will be ignored if crashkernel=X is specified.
    crashkernel=size[KMG],low
    - [KNL, x86_64] range under 4G. When crashkernel=X,high
    + [KNL, x86_64, arm64] range under 4G. When crashkernel=X,high
    is passed, kernel could allocate physical memory region
    above 4G, that cause second kernel crash on system
    that require some amount of low memory, e.g. swiotlb
    --
    2.7.4
    \
     
     \ /
      Last update: 2019-04-16 09:34    [W:2.842 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site