From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Landley <rob@landley.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 1/3] x86, boot: add mmio serial during compressed boot
Date: Sat, 13 Jul 2013 15:33:09 -0700 [thread overview]
Message-ID: <f8b2c6f6-6f00-4966-9d95-56d7ef3eb626@email.android.com> (raw)
In-Reply-To: <CAE9FiQVrq3_oeFFLVhXvfBM75frQghzy7i6r+N4gW_F-K0-n8g@mail.gmail.com>
I think we will need to map the uart explicitly, which is complex as that in turn implies seeing up something like the fixmap for the decompressor... not impossible but additional complexity to be sure. At least on 64 bits the high half should not conflict with any physical addresses.
Either that or be able to add pagetables to map the mmio directly or via a #PF handler like we already have in the early kernel.
Yinghai Lu <yinghai@kernel.org> wrote:
>On Sat, Jul 13, 2013 at 7:53 AM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 07/12/2013 11:47 PM, Yinghai Lu wrote:
>>>
>>> for 32 bit, that is ok.
>>> for 64 bit via 32bit bootloader, arch/x86/boot/compressed/head_64.S
>>> will set page table for first 4G still ok.
>>> for 64 bit via 64bit loader, like kexec via bzImage64, First
>Kernel/Kexec only
>>> set ident mapping for usable range, so mmio just under 64 is not
>mapped.
>>>
>>> Looks like we need to update boot.txt to add requirement for 64bit
>bootloader
>>> that 0-4G need to be all ident mapping?
>>>
>>
>> I think that is an unrealistic requirement, especially if this is the
>> sole user.
>
>That will cause regression for:
>64bit system with kexec/kdump bzImage64.
>if second kernel carry "console=uart,mmio,0xABCD0000"
>
>or we can extend kexec-tools to make it scan second kernel command line
>string
>and one entry into image->segment[]
>
>Yinghai
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-07-13 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 20:07 [PATCH " Kees Cook
2013-07-12 20:07 ` [PATCH 2/3] serial: report base_baud after initialization Kees Cook
2013-07-12 20:07 ` [PATCH 3/3] printk: report boot console names during cut-over Kees Cook
[not found] ` <CAGXu5jL=oSkWTGEbYLxAU1PwGbgoyeiOgFV31Gd4yj1JkDECBg@mail.gmail.com>
2013-07-12 20:17 ` [PATCH 1/3] x86, boot: add mmio serial during compressed boot Kees Cook
2013-07-12 20:20 ` H. Peter Anvin
2013-07-12 20:38 ` [PATCH v2 " Kees Cook
2013-07-13 6:47 ` Yinghai Lu
2013-07-13 14:53 ` H. Peter Anvin
2013-07-13 21:56 ` Yinghai Lu
2013-07-13 22:33 ` H. Peter Anvin [this message]
2013-07-16 19:31 ` Kees Cook
2013-07-16 19:36 ` H. Peter Anvin
2013-07-16 19:40 ` Kees Cook
2013-07-16 19:41 ` H. Peter Anvin
2013-07-16 21:59 ` Yinghai Lu
2013-07-16 21:03 ` Yinghai Lu
2013-07-16 22:05 ` H. Peter Anvin
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=f8b2c6f6-6f00-4966-9d95-56d7ef3eb626@email.android.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®