From: "H. Peter Anvin" <hpa@zytor.com>
To: Pekka Enberg <penberg@kernel.org>, Jerry Hoemann <jerry.hoemann@hp.com>
Cc: Rob Landley <rob@landley.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, x86 maintainers <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"list@ebiederm.org:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"list@ebiederm.org:MEMORY MANAGEMENT"
<linux-mm@kvack.org>linux-doc@vger.kernel.org,
linux-efi@vger.kernel.org, Vivek Goyal <vgoyal@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Early use of boot service memory
Date: Thu, 14 Nov 2013 10:45:42 -0800 [thread overview]
Message-ID: <52851A56.1040709@zytor.com> (raw)
In-Reply-To: <CAOJsxLFWMi8DoFp+ufri7XoFO27v+2=0oksh8+NhM6P-OdkOwg@mail.gmail.com>
On 11/14/2013 10:44 AM, Pekka Enberg wrote:
> On Thu, Nov 14, 2013 at 8:04 PM, <jerry.hoemann@hp.com> wrote:
>> Making this issue a quirk will be a lot more practical. Its a small, focused
>> change whose implications are limited and more easily understood.
>
> There's nothing practical with requiring users to pass a kernel option
> to make kdump work. It's a workaround, sure, but it's not a proper
> fix.
And once you have to do that anyway, you might as well just do the kdump
load high...
-hpa
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Pekka Enberg <penberg@kernel.org>, Jerry Hoemann <jerry.hoemann@hp.com>
Cc: Rob Landley <rob@landley.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, x86 maintainers <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"list@ebiederm.org:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"list@ebiederm.org:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
linux-doc@vger.kernel.org, linux-efi@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Early use of boot service memory
Date: Thu, 14 Nov 2013 10:45:42 -0800 [thread overview]
Message-ID: <52851A56.1040709@zytor.com> (raw)
In-Reply-To: <CAOJsxLFWMi8DoFp+ufri7XoFO27v+2=0oksh8+NhM6P-OdkOwg@mail.gmail.com>
On 11/14/2013 10:44 AM, Pekka Enberg wrote:
> On Thu, Nov 14, 2013 at 8:04 PM, <jerry.hoemann@hp.com> wrote:
>> Making this issue a quirk will be a lot more practical. Its a small, focused
>> change whose implications are limited and more easily understood.
>
> There's nothing practical with requiring users to pass a kernel option
> to make kdump work. It's a workaround, sure, but it's not a proper
> fix.
And once you have to do that anyway, you might as well just do the kdump
load high...
-hpa
next prev parent reply other threads:[~2013-11-14 18:45 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 2:15 [PATCH 0/3] Early use of boot service memory Jerry Hoemann
[not found] ` <1384222558-38527-1-git-send-email-jerry.hoemann-VXdhtT5mjnY@public.gmane.org>
2013-11-12 2:15 ` [PATCH 1/3] efi: " Jerry Hoemann
2013-11-12 2:15 ` Jerry Hoemann
2013-11-12 2:15 ` [PATCH 3/3] x86, " Jerry Hoemann
2013-11-12 2:15 ` Jerry Hoemann
2013-11-12 18:58 ` [PATCH 0/3] " H. Peter Anvin
2013-11-12 18:58 ` H. Peter Anvin
[not found] ` <d73ccce9-6a0d-4470-bda3-f0c6eb96b5e4-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-11-13 22:45 ` jerry.hoemann-VXdhtT5mjnY
2013-11-13 22:45 ` jerry.hoemann
[not found] ` <20131113224503.GB25344-dMAi7lA+vBPDUbYHzcRnttBPR1lH4CV8@public.gmane.org>
2013-11-13 22:49 ` H. Peter Anvin
2013-11-13 22:49 ` H. Peter Anvin
[not found] ` <52840206.5020006-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-11-13 23:57 ` jerry.hoemann-VXdhtT5mjnY
2013-11-13 23:57 ` jerry.hoemann
2013-11-14 0:05 ` H. Peter Anvin
2013-11-14 1:40 ` jerry.hoemann
[not found] ` <528413DE.1090203-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2014-08-01 9:54 ` Yuhong Bao
2014-08-01 9:54 ` Yuhong Bao
[not found] ` <20131113235708.GC25344-dMAi7lA+vBPDUbYHzcRnttBPR1lH4CV8@public.gmane.org>
2013-11-14 8:24 ` Pekka Enberg
2013-11-14 8:24 ` Pekka Enberg
2013-11-14 18:04 ` jerry.hoemann
[not found] ` <20131114180455.GA32212-dMAi7lA+vBPDUbYHzcRnttBPR1lH4CV8@public.gmane.org>
2013-11-14 18:44 ` Pekka Enberg
2013-11-14 18:44 ` Pekka Enberg
2013-11-14 18:45 ` H. Peter Anvin [this message]
2013-11-14 18:45 ` H. Peter Anvin
2013-11-15 0:50 ` jerry.hoemann
[not found] ` <20131115005049.GJ5116-dMAi7lA+vBPDUbYHzcRnttBPR1lH4CV8@public.gmane.org>
2013-11-15 6:24 ` Ingo Molnar
2013-11-15 6:24 ` Ingo Molnar
2013-11-15 6:55 ` Yinghai Lu
2013-11-15 6:59 ` H. Peter Anvin
2013-11-15 6:59 ` H. Peter Anvin
2013-11-15 14:07 ` Vivek Goyal
2013-11-15 14:07 ` Vivek Goyal
2013-11-15 17:33 ` Yinghai Lu
2013-11-15 17:33 ` Yinghai Lu
2013-11-15 17:40 ` H. Peter Anvin
2013-11-15 17:40 ` H. Peter Anvin
2013-11-15 18:30 ` Vivek Goyal
2013-11-15 18:30 ` Vivek Goyal
2013-11-15 18:46 ` H. Peter Anvin
2013-11-15 18:46 ` H. Peter Anvin
2013-11-15 19:16 ` H. Peter Anvin
2013-11-15 19:16 ` H. Peter Anvin
2013-11-18 15:22 ` Vivek Goyal
2013-11-18 15:22 ` Vivek Goyal
2013-11-18 18:29 ` H. Peter Anvin
2013-11-18 18:29 ` H. Peter Anvin
2013-11-18 18:52 ` Vivek Goyal
2013-11-18 18:52 ` Vivek Goyal
2013-11-19 1:32 ` H. Peter Anvin
2013-11-19 1:32 ` H. Peter Anvin
[not found] ` <528ABFA3.6060905-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-11-19 3:02 ` Yinghai Lu
2013-11-19 3:02 ` Yinghai Lu
2013-11-19 3:02 ` Yinghai Lu
2013-11-15 18:03 ` Vivek Goyal
2013-11-15 18:03 ` Vivek Goyal
2013-11-15 22:24 ` Yinghai Lu
2013-11-15 22:24 ` Yinghai Lu
[not found] ` <CAE9FiQU_OstEq3VWwBB879O4EY0DE+zVWVens+w0MLFUQmr3sw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-15 22:55 ` jerry.hoemann-VXdhtT5mjnY
2013-11-15 22:55 ` jerry.hoemann
2013-11-15 22:55 ` jerry.hoemann
2013-11-15 23:43 ` Yinghai Lu
2013-11-15 23:43 ` Yinghai Lu
2013-11-18 15:32 ` Vivek Goyal
2013-11-18 15:32 ` Vivek Goyal
2013-11-18 19:34 ` Yinghai Lu
2013-11-18 19:34 ` Yinghai Lu
2013-11-18 19:39 ` Vivek Goyal
2013-11-18 19:39 ` Vivek Goyal
2013-11-15 18:16 ` jerry.hoemann
2013-11-15 18:16 ` jerry.hoemann
2013-11-15 19:13 ` jerry.hoemann
2013-11-18 15:42 ` Vivek Goyal
2013-11-15 8:36 ` Pekka Enberg
2013-11-15 8:36 ` Pekka Enberg
2013-11-15 8:36 ` Pekka Enberg
2013-11-14 15:26 ` Vivek Goyal
2013-11-14 15:26 ` Vivek Goyal
2013-11-12 2:15 ` [PATCH 2/3] x86: avoid efi_reserve_boot_services Jerry Hoemann
2013-11-12 10:37 ` [PATCH 0/3] Early use of boot service memory Pekka Enberg
2013-11-12 17:55 ` jerry.hoemann
2013-11-12 18:48 ` Pekka Enberg
[not found] ` <CAOJsxLEU1SPd=1C8QPgrZGWeOuyOVkozuMR014xBpJTxyFviKA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-12 21:52 ` jerry.hoemann-VXdhtT5mjnY
2013-11-12 21:52 ` jerry.hoemann
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=52851A56.1040709@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=jerry.hoemann@hp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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.