From: Andreas Dilger <adilger@turbolabs.com>
To: Alessandro Suardi <alessandro.suardi@oracle.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
Dan Merillat <harik@chaos.ao.net>,
linux-kernel@vger.kernel.org
Subject: Re: Wierd /proc/cpuinfo with 2.4.11-pre4
Date: Fri, 5 Oct 2001 17:18:15 -0600 [thread overview]
Message-ID: <20011005171815.O315@turbolinux.com> (raw)
In-Reply-To: <1566531237.1002293911@mbligh.des.sequent.com> <3BBE3DD4.27DFFDCE@oracle.com>
In-Reply-To: <3BBE3DD4.27DFFDCE@oracle.com>
On Oct 06, 2001 01:10 +0200, Alessandro Suardi wrote:
> "Martin J. Bligh" wrote:
> > Sorry. Mea culpa
> >
> > --- setup.c.old Fri Oct 5 14:20:29 2001
> > +++ setup.c Fri Oct 5 14:28:51 2001
> > @@ -2420,7 +2420,7 @@
> > * WARNING - nasty evil hack ... if we print > 8, it overflows the
> > * page buffer and corrupts memory - this needs fixing properly
> > */
> > - for (n = 0; n < 8; n++, c++) {
> > + for (n = 0; n < (clustered_apic_mode ? 8 : NR_CPUS); n++, c++) {
> > /* for (n = 0; n < NR_CPUS; n++, c++) { */
> > int fpu_exception;
> > #ifdef CONFIG_SMP
This will also fail if, for some reason "clustered_apic_mode" is set and
you have less than 8 CPUs. What you really want is to have "max(8:NR_CPUS)"
in the loop (or make the loop actually work with > 8 CPUs, which is probably
the correct solution in the long run).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-10-05 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 18:16 Wierd /proc/cpuinfo with 2.4.11-pre4 Dan Merillat
2001-10-05 21:45 ` Alessandro Suardi
2001-10-05 21:58 ` Martin J. Bligh
2001-10-05 23:10 ` Alessandro Suardi
2001-10-05 23:07 ` Martin J. Bligh
2001-10-06 0:37 ` Alessandro Suardi
2001-10-05 23:18 ` Andreas Dilger [this message]
2001-10-05 23:20 ` Martin J. Bligh
2001-10-05 23:17 ` Brian Gerst
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=20011005171815.O315@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=alessandro.suardi@oracle.com \
--cc=harik@chaos.ao.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.