LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high
Date: Mon, 26 Jan 2015 13:40:06 +0100 [thread overview]
Message-ID: <20150126124005.GC4653@8bytes.org> (raw)
In-Reply-To: <20150126122017.GA1656@pd.tnic>
On Mon, Jan 26, 2015 at 01:20:17PM +0100, Borislav Petkov wrote:
> On Mon, Jan 26, 2015 at 01:11:42PM +0100, Joerg Roedel wrote:
> > Or we solve it in user-space by some more cleverness in creating the
> > kernel command-line for crashkernel=high.
>
> I'd say, we should try to do as much as possible automatically.
Thats hard to do, without any information about the driver needs we only
have the amount of devices in the system to base any heuristic on.
> > But besides that, I think the first two patches of this set make sense
> > anyway. I understand that the third one is debatable.
>
> Right, but since they fix a real problem, maybe we should take them now
> until a better fix is done? Yes, no?
Yes. Given that we have no data about what would work on most
systems, we can only change the value to a number that fixes know
problems and then act on possible regressions caused by the change (and
that change is pretty easy to revert if needed).
Joerg
next prev parent reply other threads:[~2015-01-26 12:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 14:51 [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Joerg Roedel
2015-01-06 14:51 ` [PATCH 1/3] swiotlb: Warn on allocation failure in swiotlb_alloc_coherent Joerg Roedel
2015-01-23 17:04 ` Borislav Petkov
2015-01-26 11:49 ` Joerg Roedel
2015-01-06 14:51 ` [PATCH 2/3] x86, swiotlb: Try coherent allocations with __GFP_NOWARN Joerg Roedel
2015-01-23 17:03 ` Borislav Petkov
2015-01-26 3:22 ` Baoquan He
2015-01-26 11:54 ` Joerg Roedel
2015-01-06 14:51 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
2015-01-23 8:44 ` Baoquan He
2015-01-26 12:07 ` Joerg Roedel
2015-02-01 8:41 ` Baoquan He
2015-02-04 14:10 ` Joerg Roedel
2015-02-09 12:20 ` Joerg Roedel
2015-02-13 15:34 ` Baoquan He
2015-02-13 22:28 ` Joerg Roedel
2015-02-14 11:44 ` Baoquan He
2015-01-23 17:02 ` Borislav Petkov
2015-01-26 12:11 ` Joerg Roedel
2015-01-26 12:20 ` Borislav Petkov
2015-01-26 12:40 ` Joerg Roedel [this message]
2015-01-26 12:45 ` Borislav Petkov
2015-01-14 13:35 ` [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Joerg Roedel
2015-01-19 19:26 ` Borislav Petkov
2015-02-14 10:58 ` Baoquan He
2015-02-14 16:11 ` Joerg Roedel
2015-06-02 8:54 ` Baoquan He
2015-06-02 9:08 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2015-06-05 10:29 [PATCH 0/3 v3] " Joerg Roedel
2015-06-05 10:30 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
2014-11-28 11:29 [PATCH 0/3] Fix kdump failures with crashkernel=high Joerg Roedel
2014-11-28 11:29 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
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=20150126124005.GC4653@8bytes.org \
--to=joro@8bytes.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).