mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: Re: [PATCH 2/2] x86_64: move apic init in init_IRQs
Date: Tue, 04 Oct 2005 09:42:12 -0600	[thread overview]
Message-ID: <m1u0fx70h7.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200510041724.36535.ak@suse.de> (Andi Kleen's message of "Tue, 4 Oct 2005 17:24:36 +0200")

Andi Kleen <ak@suse.de> writes:

> On Tuesday 04 October 2005 17:13, Eric W. Biederman wrote:
>> All kinds of ugliness exists because we don't initialize
>> the apics during init_IRQs.
>> - We calibrate jiffies in non apic mode even when we are using apics.
>> - We have to have special code to initialize the apics when non-smp.
>> - The legacy i8259 must exist and be setup correctly, even
>>   we won't use it past initialization.
>
> Actually some setups use its timer even in ACPI mode. Do you take this into 
> account?

The patch is basically code motion and duplication removal with just a
few tweaks thrown in to account for the change in location in the
kernel boot process when all of occurs.

So everything that was working should continue to work.

> In theory it looks reasonable, but I guess it won't work without the bogus
> watchdog change. That would need to be resolved first.

Sure.  That should be straight forward.  The only part that breaks is
the watchdog initialization/testing.  As I recall there was no obvious
place to put it.  The call has to happen after everything is running
so it is a bit tricky to find a good place to put it.

Eric


  reply	other threads:[~2005-10-04 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04 15:13 Eric W. Biederman
2005-10-04 15:24 ` Andi Kleen
2005-10-04 15:42   ` Eric W. Biederman [this message]
2005-10-05 19:36   ` [PATCH] x86_64: move apic init in init_IRQs (take 2) 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=m1u0fx70h7.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=fastboot@osdl.org \
    --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

all inboxes | Powered by JetHome®