From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] early console registration
Date: Wed, 16 Jun 2004 20:22:06 +0000 [thread overview]
Message-ID: <200406161422.06366.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200405141425.59867.jbarnes@engr.sgi.com>
On Tuesday 15 June 2004 7:12 am, Jesse Barnes wrote:
> 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.
It's *not* online as soon as it starts head.S, though -- that's what I
meant about preserving the original cpu_online semantics. It currently
means that at least cpu_init() has been called, so memory allocation,
per-cpu data, and interrupts should work.
If we mark CPU 0 as 'online' earlier, some hypothetical new code could
test cpu_online(0) and incorrectly assume per-cpu data works.
But AFAIK, there is no such code now, and I don't have any better ideas,
so maybe we should just go with your ia64-specific patch for now.
next prev parent reply other threads:[~2004-06-16 20:22 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
2004-06-16 20:22 ` Bjorn Helgaas [this message]
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=200406161422.06366.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.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