public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Kees Cook <keescook@chromium.org>
Cc: Yinghai Lu <yinghai@kernel.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-doc@vger.kernel.org>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 1/3] x86, boot: add mmio serial during compressed boot
Date: Tue, 16 Jul 2013 12:36:09 -0700	[thread overview]
Message-ID: <51E5A0A9.90108@zytor.com> (raw)
In-Reply-To: <CAGXu5jJs5ve-31AYKbv6EaV5PKCf5cOEeWTRsYsi_kBbLWj5uQ@mail.gmail.com>

On 07/16/2013 12:31 PM, Kees Cook wrote:
> 
> Could the first step be documenting the limitation? I've found this
> patch extremely useful for my case already, and I imagine there might
> be other people that need the early mmio stuff to. Generally the
> compressed boot serial console stuff is going to be used in the more
> common non-kexec situations at least for a while.
> 
> Does this patch create any _problems_? Right now, neither low nor >4G
> kernel can use an mmio serial port. :) This this, we'd at least gain
> it for the low case.
> 

Even documenting the limitation is likely to end up with a bunch of
emails asking why their kernel crashed.

I think setting up a dynamic #PF handler is the right thing for the
decompressor, we already did for the kernel proper.

	-hpa



  reply	other threads:[~2013-07-16 19:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 20:07 [PATCH 1/3] x86, boot: add mmio serial during compressed boot 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
2013-07-16 19:31     ` Kees Cook
2013-07-16 19:36       ` H. Peter Anvin [this message]
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=51E5A0A9.90108@zytor.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