lkml.org 
[lkml]   [2011]   [Aug]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [patch v2 01/10] kdump: Add KEXEC_CRASH_CONTROL_MEMORY_LIMIT
    From
    Date
    Hello Vivek,

    On Mon, 2011-08-01 at 16:16 -0400, Vivek Goyal wrote:
    > On Wed, Jul 27, 2011 at 02:55:05PM +0200, Michael Holzheu wrote:
    > > From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
    > >
    > > On s390 there is a different KEXEC_CONTROL_MEMORY_LIMIT for the normal and
    > > the kdump kexec case. Therefore this patch introduces a new macro
    > > KEXEC_CRASH_CONTROL_MEMORY_LIMIT. This is set to
    > > KEXEC_CONTROL_MEMORY_LIMIT for all architectures that do not define
    > > KEXEC_CRASH_CONTROL_MEMORY_LIMIT.
    >
    > Hi Michael,
    >
    > Curious that why limit is different for kexec and kdump cases on s390
    > only.

    The standard kexec relocate_kernel code calls a machine instruction that
    must run below 2 GiB. For kdump we currently do not use the control page
    at all because no segments have to be moved in that case. Perhaps I am
    still missing something here?

    Michael



    \
     
     \ /
      Last update: 2011-08-02 11:53    [W:0.021 / U:1.168 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site