From: "Jan Beulich" <JBeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: x86-64/kexec: crashkernel= without @xM suffix
Date: Fri, 30 Apr 2010 07:42:06 +0100 [thread overview]
Message-ID: <4BDA97DE0200007800000C43@vpn.id2.novell.com> (raw)
Was this ever tested by anyone? Has it ever worked with any Linux
as secondary kernel? We're getting reports (and analysis confirms
this) that the fact that Xen places the hole at the highest suitable
address below 4G prevents kexec from working.
A possible fix is non-obvious, since there doesn't appear to be a
hard boundary below which the hole must reside (especially for a
32-bit secondary kernel; for a 64-bit one it seems like any place
below 2G would be acceptable).
Simply using Linux' strategy and allocating at the lowest possible
address doesn't seem too nice a solution either, as we try to
conserve on the use of low memory as much as possible almost
everywhere else.
Thanks, Jan
next reply other threads:[~2010-04-30 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 6:42 Jan Beulich [this message]
2010-05-02 2:21 ` x86-64/kexec: crashkernel= without @xM suffix Simon Horman
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=4BDA97DE0200007800000C43@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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).