The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Itsuro Oda <oda@valinux.co.jp>
Cc: fastboot <fastboot@lists.osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Re: kdump on non-boot cpu
Date: 07 Feb 2005 00:37:36 -0700	[thread overview]
Message-ID: <m1ekfs3jnj.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050204144438.18F9.ODA@valinux.co.jp>

Itsuro Oda <oda@valinux.co.jp> writes:

> > So I believe the fix needs to be to enable apics before we calibrate
> > the delay timer.  I'm not certain off the top of my head what that
> > patch will look like but it should not be fundamentally hard.  
> > With that code in place we also don't need to do any APIC shutdown
> > as the kernel knows enough to completely setup the apics.
> 
> I see. Thank you for your explanation.

I have done a bit more digging.

For some reason, likely historical we don't initialize the
IO_APIC in init_IRQ().  Instead we wait until smp_prepare_cpus() or
smp_init().  Both functions are called much later in the init process
than calibrate_delay().

Given the separation that has happened between apics and SMP it should
be possible to initialize the local apic and the IO_APIC of the boot
cpu much earlier in the game.  It looks like it may take some heavy
lifting though.

Eric

      reply	other threads:[~2005-02-07  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  5:12 kdump on non-boot cpu Itsuro Oda
2005-02-03  6:42 ` Vivek Goyal
2005-02-03  8:37   ` Itsuro Oda
2005-02-03  9:58     ` [Fastboot] " Eric W. Biederman
2005-02-03 23:43       ` Itsuro Oda
2005-02-04  0:55         ` Eric W. Biederman
2005-02-04  6:02           ` Itsuro Oda
2005-02-07  7:37             ` Eric W. Biederman [this message]

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=m1ekfs3jnj.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oda@valinux.co.jp \
    /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