public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] early console registration
Date: Tue, 15 Jun 2004 13:12:41 +0000	[thread overview]
Message-ID: <200406150912.41293.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200405141425.59867.jbarnes@engr.sgi.com>

On Monday, June 14, 2004 6:27 pm, Bjorn Helgaas wrote:
> On Thursday 03 June 2004 3:49 pm, Jesse Barnes wrote:
> > Allow consoles to be registered early if they support doing output very
> > early in the boot process.  Consoles that allow this are subject to the
> > limitations outlined in the comments for the early_console_setup routine.
>
> (See original mail with patch here:
>     http://www.gelato.unsw.edu.au/linux-ia64/0406/9894.html)
>
> I'm still a little uneasy about setting cpu_online for CPU 0 so early.
> What if somebody comes along in the future and assumes the original
> semantics for cpu_online(0)?
>
> As another possibility, the following is a little more intrusive to
> printk.c, but also a little more explicit about what we're doing
> (untested).

Yeah, that's fine.  In fact, I've tested something similar and sent it to 
Andrew, but he came back and asked why not just set CPU 0 online early?  And 
given that CPU 0 is 'online' as soon as the kernel starts executing head.S, 
it seems like it *should* keep working, and we should probably keep it that 
way.

But either way is fine with me, so long as it gets upstream somehow.

Jesse

  parent reply	other threads:[~2004-06-15 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 21:25 [PATCH] early console registration Jesse Barnes
2004-05-20  1:17 ` David Mosberger
2004-05-20 13:03 ` Jesse Barnes
2004-05-20 15:18 ` Bjorn Helgaas
2004-05-20 15:26 ` Jesse Barnes
2004-06-03 21:49 ` Jesse Barnes
2004-06-14 22:27 ` Bjorn Helgaas
2004-06-15 13:12 ` Jesse Barnes [this message]
2004-06-16 20:22 ` Bjorn Helgaas
2004-06-16 20:40 ` Jesse Barnes
2004-06-22 17:54 ` Jesse Barnes

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=200406150912.41293.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=linux-ia64@vger.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