All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Warner Wang <warner.wang@hp.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: keep the crash kernel below 896 MiB
Date: Thu, 25 Apr 2013 11:48:09 +0100	[thread overview]
Message-ID: <517909E9.2010100@citrix.com> (raw)
In-Reply-To: <517918B502000078000D0A56@nat28.tlf.novell.com>

On 25/04/13 10:51, Jan Beulich wrote:
>>>> On 25.04.13 at 10:57, Warner Wang <warner.wang@hp.com> wrote:
>> When use the crashkernel=size parameter without specifying a "@xM"
>> suffix, the crashkernel will be reserved at the highest suitable
>> address of memory, this will make the kexec-tools fail to work.
>> The current kexec-tools have a limitation that it can only work
>> with crashkernel reserved under 896 MiB.  we can increase this
>> limit once kexec-tools are fixed.
>> Linux kernel itself have this code for kexec-tools limitation,
>> so I think Xen code should also have it.
> Andrew,
>
> didn't you post something along those lines at some point too,
> yet there was a reason it never got applied?
>
> Jan

Jan:
I have some low crashinfo patches but they are in.  It was for
positioning of the Xen per-cpu crash notes and the console ring.

Warner:
I am curious to know what this magic 896MiB limit is.  Do you have a
reference to the problem.

~Andrew

>
>> --- a/xen/arch/x86/setup.c
>> +++ b/xen/arch/x86/setup.c
>> @@ -943,6 +943,13 @@ void __init __start_xen(unsigned long mbi_p)
>>              }
>>          }
>>  
>> +        /*
>> +         * Keep the crash kernel below this limit.  On 64 bits, kexec-tools
>> +         * currently limits us to 896 MiB; increase this limit once kexec-tools
>> +         * are fixed.
>> +         */
>> +        e = min_t(uint64_t, e, 896 << 20);
>> +
>>          /* Don't overlap with modules. */
>>          e = consider_modules(s, e, PAGE_ALIGN(kexec_crash_area.size),
>>                               mod, mbi->mods_count, -1);
>> -- 
>> 1.7.1
>
>

  reply	other threads:[~2013-04-25 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  8:57 [PATCH] x86: keep the crash kernel below 896 MiB Warner Wang
2013-04-25  9:51 ` Jan Beulich
2013-04-25 10:48   ` Andrew Cooper [this message]
2013-04-25 11:01 ` David Vrabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=517909E9.2010100@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=warner.wang@hp.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.