public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 2.4 1/2] backport 2.6 x86 cpu capabilities
Date: Sat, 09 Aug 2003 10:05:18 -0400	[thread overview]
Message-ID: <3F34FF9E.8080005@pobox.com> (raw)
In-Reply-To: <200308081941.h78JfDKa029002@harpo.it.uu.se>

Mikael Pettersson wrote:
> On Fri, 08 Aug 2003 09:15:03 -0400, Jeff Garzik wrote:
> 
>>>If you change NCAPINTS you also have to change the hardcoded
>>>struct offset X86_VENDOR_ID in arch/i386/kernel/head.S. Otherwise
>>>nasty stuff happen at boot since boot_cpu_data gets broken.
>>
>>
>>hmmm, reality doesn't seem to bear that out...  I made the same change 
>>to 2.6, without touching head.S, and life continues without "nasty 
>>stuff" AFAICS.
>>
>>Do both 2.4 and 2.6 need this change?  And, why didn't 2.6 break?
> 
> 
> 2.4.21-rc1 with NCAPINTS==6 hangs at boot in the local
> APIC timer calibration step; before that it detected a
> 0MHz bus clock and the local APIC NMI watchdog was stuck.
> Correcting head.S:X86_VENDOR_ID fixes these problems.
> 
> Without correcting head.S:X86_VENDOR_ID, head.S will store
> the vendor id partly in the capabilities array. This breaks
> both the capabilities and the vendor id. I can't say why 2.6
> works, but obviously the CPU setup code has changed since 2.4.
> 
> BTW, the patch below should be applied to 2.6.


Thanks for the patch, and for explaining.

	Jeff




  reply	other threads:[~2003-08-09 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 19:41 [patch 2.4 1/2] backport 2.6 x86 cpu capabilities Mikael Pettersson
2003-08-09 14:05 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-10 23:59 Albert Cahalan
2003-08-11  0:28 ` Jeff Garzik
2003-08-08 11:19 Mikael Pettersson
2003-08-08 13:15 ` Jeff Garzik
2003-08-09  9:51   ` Marc-Christian Petersen
2003-08-08  2:54 Jeff Garzik

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=3F34FF9E.8080005@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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