From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Jeff Garzik <jgarzik@pobox.com>, 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, 9 Aug 2003 11:51:23 +0200 [thread overview]
Message-ID: <200308091150.59006.m.c.p@wolk-project.de> (raw)
In-Reply-To: <3F33A257.7050101@pobox.com>
On Friday 08 August 2003 15:15, Jeff Garzik wrote:
Hi Jeff,
> >>-#define NCAPINTS 4 /* Currently we have 4 32-bit words worth of info */
> >>+#define NCAPINTS 6 /* Currently we have 6 32-bit words worth of info */
> > 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?
Mikael is right. At least 2.4 need this change, otherwise APIC may break.
2.6 might break also in some cases.
ciao, Marc
next prev parent reply other threads:[~2003-08-09 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 11:19 [patch 2.4 1/2] backport 2.6 x86 cpu capabilities Mikael Pettersson
2003-08-08 13:15 ` Jeff Garzik
2003-08-09 9:51 ` Marc-Christian Petersen [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 19:41 Mikael Pettersson
2003-08-09 14:05 ` Jeff Garzik
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=200308091150.59006.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=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;
as well as URLs for NNTP newsgroup(s).