From: "H. Peter Anvin" <hpa@zytor.com>
To: Neil Horman <nhorman@redhat.com>
Cc: kexec@lists.infradead.org, ebiederm@xmission.com,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: Question regardin intel64 arch and page table setup
Date: Wed, 11 Aug 2010 18:46:16 -0700 [thread overview]
Message-ID: <4C635268.1030709@zytor.com> (raw)
In-Reply-To: <20100812010506.GB2258@localhost.localdomain>
On 08/11/2010 06:05 PM, Neil Horman wrote:
>
> Thanks for all the info, guys. I hadn't considered that we couldn't access the
> 64 bit startup point for the bzImage. I just figured we could jump to
> startup_32 + 0x200 in the bzImage header once I had the page table bit set up
> properly.
>
> I hadn't considered the problems we might encounter with driver issues loading
> above 4gb and what have you, nor the starting of AP's.
>
> Regardless, I'll keep tinkering. One more question. When setting up the page
> table in the panic boot case, is it sufficient to setup an identity map for the
> pages in the reserved crashkernel range, or do we need to identity map the
> entire range of ram?
>
Not clear to me. Probably the former, but you might find problems.
Another issue: if you are planning to run SMP, the AP trampoline needs
low memory, too.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-08-12 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 19:47 Question regardin intel64 arch and page table setup Neil Horman
2010-08-11 20:02 ` H. Peter Anvin
2010-08-11 21:51 ` Eric W. Biederman
2010-08-11 21:54 ` Eric W. Biederman
2010-08-11 22:02 ` H. Peter Anvin
2010-08-12 0:22 ` Eric W. Biederman
2010-08-12 1:05 ` Neil Horman
2010-08-12 1:46 ` H. Peter Anvin [this message]
2010-08-12 1:53 ` H. Peter Anvin
2010-08-12 3:21 ` Eric W. Biederman
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=4C635268.1030709@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
--cc=nhorman@tuxdriver.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 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.