From: "David Luyer" <david@luyer.net>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Linux 2.4.19ac3rc3 on IBM x330/x340 SMP - "ps" time skew
Date: Wed, 31 Jul 2002 23:57:09 +1000 [thread overview]
Message-ID: <00d101c2389a$29995970$638317d2@pacific.net.au> (raw)
In-Reply-To: <1028127891.8510.79.camel@irongate.swansea.linux.org.uk>
> > Possibly because show_cpuinfo() in arch/i386/kernel/setup.c prints
> > directly out of phys_proc_id as at the time it's called, but
> > smpboot.c declates phys_proc_id as __initdata (either that, or
> > phys_proc_id is actually zero for both CPUs?).
>
> The former is the problem. Thanks for spotting it. As to the text
> string, I'll have a chat with Ulrich about it and see what he thinks
The former and the latter possibly: the only assignment I see for
phys_proc_id is when hyperthreading is happening (in fact, requires
all of X86_FEATURE_HT, !disable_x86_ht and smp_num_siblings > 1);
down the end of kernel/setup.c init_intel().
David.
next prev parent reply other threads:[~2002-07-31 13:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 11:01 David Luyer
2002-07-31 13:28 ` Alan Cox
2002-07-31 12:59 ` David Luyer
2002-07-31 14:26 ` Alan Cox
2002-07-31 13:18 ` David Luyer
2002-07-31 13:31 ` Dana Lacoste
2002-07-31 13:38 ` David Luyer
2002-07-31 15:04 ` Alan Cox
2002-07-31 13:57 ` David Luyer [this message]
2002-07-31 16:15 ` NMI watchdog, die(), & console_loglevel Jonathan Lundell
2002-07-31 19:14 ` Linux 2.4.19ac3rc3 on IBM x330/x340 SMP - "ps" time skew Albert D. Cahalan
2002-08-01 0:37 ` Alan Cox
2002-07-31 23:49 ` Dave Jones
2002-08-01 1:30 ` Alan Cox
2002-08-01 0:19 ` Dave Jones
2002-07-31 23:42 ` Lincoln Dale
2002-08-01 1:33 ` Albert D. Cahalan
2002-08-01 3:34 ` Martin J. Bligh
2002-08-01 14:16 ` Alan Cox
2002-08-01 8:49 ` Benjamin Herrenschmidt
2002-08-01 11:40 ` Lincoln Dale
2002-08-01 18:26 ` Albert D. Cahalan
2002-08-01 14:15 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 2:46 David Luyer
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='00d101c2389a$29995970$638317d2@pacific.net.au' \
--to=david@luyer.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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®