From: Stefan Smietanowski <stesmi@stesmi.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs (resend)
Date: Tue, 27 Sep 2005 01:31:20 +0200 [thread overview]
Message-ID: <433884C8.9050905@stesmi.com> (raw)
In-Reply-To: <1127773707.8195.145.camel@cog.beaverton.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
john stultz wrote:
> On Tue, 2005-09-27 at 00:15 +0200, Stefan Smietanowski wrote:
>
>
>>Wouldn't it be a good idea to change the comment following
>>the code you removed as well?
>>
>>Why have a comment saying "multi socket systems" if there is no
>>distinction anymore?
>>
> Yea, good point, that should probably be "SMP systems".
>
> Do you want to send the patch to Andrew? :)
Sure. Something like this should suffice.
Signed-off-by: Stefan Smietanowski <stesmi@stesmi.com>
diff --git old/arch/x86_64/kernel/time.c new/arch/x86_64/kernel/time.c
- --- old/arch/x86_64/kernel/time.c
+++ new/arch/x86_64/kernel/time.c
@@ -959,11 +959,8 @@ static __init int unsynchronized_tsc(voi
are handled in the OEM check above. */
if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL)
return 0;
- - /* All in a single socket - should be synchronized */
- - if (cpus_weight(cpu_core_map[0]) == num_online_cpus())
- - return 0;
#endif
- - /* Assume multi socket systems are not synchronized */
+ /* Assume SMP systems are not synchronized */
return num_online_cpus() > 1;
}
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFDOITIBrn2kJu9P78RAopLAJ0anLvWElwgW+vmxJ7jPWehWF0F3gCfUXv8
2ORxa8Jfj9o4LE3P0A+dSTE=
=AGkR
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-09-26 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 19:46 [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs (resend) john stultz
2005-09-26 20:33 ` Andrew Morton
2005-09-27 8:34 ` Andi Kleen
2005-09-26 22:15 ` Stefan Smietanowski
2005-09-26 22:28 ` john stultz
2005-09-26 23:31 ` Stefan Smietanowski [this message]
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=433884C8.9050905@stesmi.com \
--to=stesmi@stesmi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--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