From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
WANG Chao <chaowang@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, kdump: Set crashkernel_low automatically
Date: Mon, 11 Mar 2013 12:04:38 -0700 [thread overview]
Message-ID: <513E2AC6.1000707@zytor.com> (raw)
In-Reply-To: <20130311190242.GC12107@redhat.com>
On 03/11/2013 12:02 PM, Vivek Goyal wrote:
>>
>> What is the purpose of reserving that kind of memory below 896 MB? If
>> you have a 32-bit system, it will likely be useless since you are
>> robbing the primary of most of lowmem, on a 64-bit system 896 MB is not
>> a magic value in any way...?
>
> Actually I am not sure where did 896MB magic value had come from for
> x86_64 so far. I assumed that it was some kexec-tools limitation so
> first trying 896MB will preserve working with old kexec-tools. If it
> was some kernel limitation, then I agree it should not be required anymore.
>
> I do remember that old pugatory had 2G limit. So may be we can first
> try reserve with-in first 2G, then with-in first 4G and then above
> 4G. (Assuming 896M was not kexec-tools limitation and had something
> to do with kernel/initramfs).
>
It is obvious where it *originated* from... it is the *default* (but not
necessarily the actual!) HIGHMEM crossover point on x86-32.
Whether this limitation has crept into somewhere else is a good question.
-hpa
next prev parent reply other threads:[~2013-03-11 19:07 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 5:54 3.9-rc1: crash kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer WANG Chao
2013-03-08 6:03 ` CAI Qian
2013-03-08 6:03 ` CAI Qian
2013-03-08 6:32 ` Yinghai Lu
2013-03-08 6:32 ` Yinghai Lu
2013-03-08 6:36 ` Yinghai Lu
2013-03-08 6:36 ` Yinghai Lu
2013-03-08 7:20 ` WANG Chao
2013-03-08 7:20 ` WANG Chao
2013-03-08 7:27 ` Yinghai Lu
2013-03-08 7:27 ` Yinghai Lu
2013-03-08 7:33 ` WANG Chao
2013-03-08 7:33 ` WANG Chao
2013-03-08 7:50 ` Yinghai Lu
2013-03-08 7:50 ` Yinghai Lu
2013-03-08 12:12 ` WANG Chao
2013-03-08 18:24 ` Yinghai Lu
2013-03-08 18:24 ` Yinghai Lu
2013-03-08 19:39 ` Yinghai Lu
2013-03-08 19:39 ` Yinghai Lu
2013-03-11 3:42 ` WANG Chao
2013-03-11 3:42 ` WANG Chao
2013-03-11 4:56 ` [PATCH] x86, kdump: Set crashkernel_low automatically Yinghai Lu
2013-03-11 14:48 ` Vivek Goyal
2013-03-11 15:02 ` Vivek Goyal
2013-03-11 17:58 ` Yinghai Lu
2013-03-11 18:26 ` Vivek Goyal
2013-03-11 18:44 ` Yinghai Lu
2013-03-11 18:46 ` H. Peter Anvin
2013-03-11 18:50 ` Yinghai Lu
2013-03-11 18:55 ` H. Peter Anvin
2013-03-11 19:06 ` Yinghai Lu
2013-03-11 19:06 ` H. Peter Anvin
2013-03-11 19:08 ` Yinghai Lu
2013-03-11 19:20 ` Vivek Goyal
2013-03-11 19:55 ` H. Peter Anvin
2013-03-11 20:12 ` Vivek Goyal
2013-03-11 20:19 ` H. Peter Anvin
2013-03-11 20:36 ` H. Peter Anvin
2013-03-11 20:38 ` Eric W. Biederman
2013-03-11 20:42 ` H. Peter Anvin
2013-03-11 21:10 ` Vivek Goyal
2013-03-11 21:13 ` H. Peter Anvin
2013-03-11 20:45 ` Vivek Goyal
2013-03-11 20:50 ` H. Peter Anvin
2013-03-11 21:03 ` Vivek Goyal
2013-03-11 21:06 ` H. Peter Anvin
2013-03-12 13:46 ` Vivek Goyal
2013-03-12 8:35 ` Ingo Molnar
2013-03-11 20:57 ` Yinghai Lu
2013-03-11 21:06 ` Vivek Goyal
2013-03-11 21:15 ` Yinghai Lu
2013-03-11 19:10 ` Vivek Goyal
2013-03-11 19:34 ` Yinghai Lu
2013-03-11 19:38 ` Vivek Goyal
2013-03-11 19:39 ` Yinghai Lu
2013-03-11 19:44 ` Vivek Goyal
2013-03-11 19:44 ` Yinghai Lu
2013-03-18 14:46 ` Vivek Goyal
2013-03-18 15:33 ` Vivek Goyal
2013-03-18 19:05 ` Yinghai Lu
2013-03-18 19:10 ` H. Peter Anvin
2013-03-18 20:00 ` Vivek Goyal
2013-03-18 21:14 ` H. Peter Anvin
2013-03-18 21:25 ` [PATCH v3] " Yinghai Lu
2013-03-18 22:52 ` H. Peter Anvin
2013-03-18 23:26 ` Yinghai Lu
2013-03-19 0:27 ` H. Peter Anvin
2013-03-19 1:04 ` [PATCH v4] " Yinghai Lu
2013-03-19 13:33 ` Vivek Goyal
2013-03-19 15:05 ` [PATCH v5] " Yinghai Lu
2013-03-20 13:08 ` Vivek Goyal
2013-03-20 15:53 ` Yinghai Lu
2013-03-20 16:03 ` Vivek Goyal
2013-03-20 16:21 ` Yinghai Lu
2013-03-20 16:31 ` Vivek Goyal
2013-03-20 19:22 ` [PATCH] kexec: use Crash kernel for Crash kernel low Yinghai Lu
2013-03-25 19:42 ` Vivek Goyal
2013-03-25 21:50 ` Yinghai Lu
2013-03-26 18:14 ` Vivek Goyal
2013-04-01 13:34 ` Vivek Goyal
2013-04-01 18:33 ` H. Peter Anvin
2013-04-01 19:26 ` Vivek Goyal
2013-04-01 20:47 ` H. Peter Anvin
2013-04-01 21:10 ` Yinghai Lu
2013-04-01 22:02 ` H. Peter Anvin
2013-04-01 22:17 ` Yinghai Lu
2013-04-01 22:20 ` H. Peter Anvin
2013-04-01 22:40 ` Yinghai Lu
2013-04-02 1:11 ` Yinghai Lu
2013-04-02 13:50 ` Vivek Goyal
2013-04-02 14:17 ` Vivek Goyal
2013-04-02 14:50 ` Yinghai Lu
2013-04-02 14:45 ` Yinghai Lu
2013-04-02 14:58 ` Vivek Goyal
2013-04-02 15:44 ` Yinghai Lu
2013-04-02 15:39 ` Vivek Goyal
2013-04-02 15:46 ` Yinghai Lu
2013-04-02 15:50 ` Vivek Goyal
2013-04-02 17:21 ` Yinghai Lu
2013-04-02 13:30 ` Vivek Goyal
2013-03-20 19:24 ` [PATCH] kdump, x86: Process multiple Crash kernel in /proc/iomem Yinghai Lu
2013-03-22 17:59 ` Vivek Goyal
2013-03-22 20:52 ` Yinghai Lu
2013-03-22 21:21 ` Vivek Goyal
2013-03-22 21:27 ` H. Peter Anvin
2013-03-22 21:35 ` Yinghai Lu
2013-03-22 21:32 ` Yinghai Lu
2013-03-11 19:14 ` [PATCH] x86, kdump: Set crashkernel_low automatically Eric W. Biederman
2013-03-11 19:22 ` Vivek Goyal
2013-03-11 19:59 ` H. Peter Anvin
2013-03-11 20:17 ` Vivek Goyal
2013-03-11 19:56 ` H. Peter Anvin
2013-03-11 19:02 ` Vivek Goyal
2013-03-11 19:04 ` H. Peter Anvin [this message]
2013-03-11 19:17 ` Vivek Goyal
2013-03-11 13:14 ` 3.9-rc1: crash kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer Konrad Rzeszutek Wilk
2013-03-11 13:14 ` Konrad Rzeszutek Wilk
2013-03-08 7:52 ` Takao Indoh
2013-03-08 7:52 ` Takao Indoh
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=513E2AC6.1000707@zytor.com \
--to=hpa@zytor.com \
--cc=chaowang@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=yinghai@kernel.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.