public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Horms <horms@verge.net.au>
Cc: linux-kernel@vger.kernel.org, fastboot@lists.osdl.org
Subject: Re: [PATCH] i386 kexec:  Allow the kexec on panic support to compile on voyager.
Date: Tue, 11 Jul 2006 14:07:24 -0600	[thread overview]
Message-ID: <m1ejwrgb2b.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060711123017.5F15A3403D@koto.vergenet.net> (horms@verge.net.au's message of "Tue, 11 Jul 2006 21:30:17 +0900 (JST)")

Horms <horms@verge.net.au> writes:

> On Mon, 10 Jul 2006 16:37:49 -0600, Eric W. Biederman wrote:
>> 
>> This patch removes the foolish assumption that SMP implied local
>> apics.  That assumption is not-true on the Voyager subarch.  This
>> makes that dependency explicit, and allows the code to build.
>
> Doesn't only a small portion of the code in question rely
> on CONFIG_X86_LOCAL_APIC? Is just a workaround until proper
> voager support materialises?

Essentially, but it is correct for the code to stay this way.

>> What gets disabled is just an optimization to get better crash
>> dumps so the support should work if there is a kernel that will
>> initialization on the voyager subarch under those harsh conditions.
>
> By that do you mean, a crash kernel that is able to boot even
> though the non-crashing CPUs have not been shutdown?

I simply mean a crash kernel that is able to boot.

>> Hopefully we can figure out how to initialize apics in init_IRQ
>> and remove the need to disable io_apics and this dependency.
>
> That does sound nice. Do you have any ideas on how that could be 
> made to happen?

My patch for that got reverted because it wouldn't boot on Linus's
SMP laptop.  It appeared to be some weird ACPI problem.  I didn't
receive any bug reports otherwise.

So I suspect the steps are:
1) Unify SMP and non-SMP apic initialization so it is the exact same
   code.
2) Move the unified code up in the boot sequence into init_IRQs.

It is something that needs to be done very delicately.

Eric

  reply	other threads:[~2006-07-11 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 22:37 [PATCH] i386 kexec: Allow the kexec on panic support to compile on voyager Eric W. Biederman
2006-07-11 12:30 ` Horms
2006-07-11 20:07   ` Eric W. Biederman [this message]
2006-07-12  1:00     ` Horms
2006-07-12  6:09       ` 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=m1ejwrgb2b.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@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