From: Simon Horman <horms@verge.net.au>
To: "Ramsay, Frank" <frank.ramsay@hpe.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Dave Young <dyoung@redhat.com>, Xunlei Pang <xlpang@redhat.com>
Subject: Re: [PATCH] x86: Support large number of memory ranges
Date: Fri, 24 Mar 2017 07:44:12 +0100 [thread overview]
Message-ID: <20170324064412.GF1319@verge.net.au> (raw)
In-Reply-To: <CS1PR84MB01983072D64758E237736825833F0@CS1PR84MB0198.NAMPRD84.PROD.OUTLOOK.COM>
On Thu, Mar 23, 2017 at 01:27:08PM +0000, Ramsay, Frank wrote:
> ________________________________________
> From: Xunlei Pang <xlpang@redhat.com>
> Sent: Thursday, March 23, 2017 7:16:59 AM
> To: kexec@lists.infradead.org
> Cc: Dave Young; Xunlei Pang; Ramsay, Frank
> Subject: [PATCH] x86: Support large number of memory ranges
>
> We got a problem on one SGI 64TB machine, the current kexec-tools
> failed to work due to the insufficient ranges(MAX_MEMORY_RANGES)
> allowed which is defined as 1024(less than the ranges on the machine).
> The kcore header is insufficient due to the same reason as well.
>
> To solve this, this patch simply doubles "MAX_MEMORY_RANGES" and
> "KCORE_ELF_HEADERS_SIZE".
>
> Cc: Frank Ramsay <frank.ramsay@hpe.com>
> Signed-off-by: Xunlei Pang <xlpang@redhat.com>
>
> acking I tested this
> Tested-by: Frank Ramsay <frank.ramsay@hpe.com>
Thanks, applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-03-24 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 11:16 [PATCH] x86: Support large number of memory ranges Xunlei Pang
2017-03-23 13:27 ` Ramsay, Frank
2017-03-24 6:44 ` Simon Horman [this message]
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=20170324064412.GF1319@verge.net.au \
--to=horms@verge.net.au \
--cc=dyoung@redhat.com \
--cc=frank.ramsay@hpe.com \
--cc=kexec@lists.infradead.org \
--cc=xlpang@redhat.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