From: Simon Horman <horms@verge.net.au>
To: Peter Chubb <peter.chubb@nicta.com.au>
Cc: kexec@lists.infradead.org
Subject: Re: kexec-tools and multiboot breakage
Date: Wed, 15 Jan 2014 12:48:33 +0900 [thread overview]
Message-ID: <20140115034833.GA30883@verge.net.au> (raw)
In-Reply-To: <84k3e2lyde.wl%peter.chubb@nicta.com.au>
On Wed, Jan 15, 2014 at 01:25:49PM +1000, Peter Chubb wrote:
> Hi Simon,
> When you get a moment, please check out
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735360
>
> Quick summary:
> If your kernel is configured to protect the first few pages of
> physical memory, then low memory doesn't start at location 0 --- so
> when scanning the memory ranges from /proc/iomem, the code in
> kexec/arch/i386/kexec-multiboot-x86.c never fills in mem_lower.
>
> I think it's safe to assume that if a memory segment starts at 64k or
> lower, it can be extended to location 0 because of the kernel
> protection on a PC99-style architecture.
Hi Peter,
that approach seems reasonable to me. Could you formally post
the patch to the kexec list with me CCed? I would like a Signed-off-by
line. Thanks.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-01-15 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 3:25 kexec-tools and multiboot breakage Peter Chubb
2014-01-15 3:48 ` Simon Horman [this message]
2014-01-15 21:39 ` [PATCH] Fix value of mbi->mem_lower for multiboot-x86 Peter Chubb
2014-01-16 0:22 ` 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=20140115034833.GA30883@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=peter.chubb@nicta.com.au \
/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