From: Jonas Oreland <jonas@mysql.com>
To: "Vladimir B. Savkin" <master@sectorb.msk.ru>
Cc: john stultz <johnstul@us.ibm.com>, Andi Kleen <ak@suse.de>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
discuss@x86-64.org
Subject: Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
Date: Tue, 11 Oct 2005 18:27:21 +0200 [thread overview]
Message-ID: <434BE7E9.8000501@mysql.com> (raw)
In-Reply-To: <20051011073532.GA29254@tentacle.sectorb.msk.ru>
Vladimir B. Savkin wrote:
> On Mon, Oct 10, 2005 at 08:19:42PM +0200, Jonas Oreland wrote:
>
>>Hi,
>>
>>check http://bugzilla.kernel.org/show_bug.cgi?id=5283
>
>
> Excuse me for possibly dumb question, but is it safe to leave TSCs
> unsynchronized when using other time source?
> How will other subsystems e.g. traffic queueing disciplines react?
Excuse me for possibly dumb answer: (i'm not a kernel hacker)
yes, I would guess that this will be handled as any other
SMP machine where TSCs arent in sync.
/Jonas
next prev parent reply other threads:[~2005-10-11 16:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 19:16 [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs john stultz
2005-09-19 19:31 ` Andi Kleen
2005-09-19 19:42 ` john stultz
2005-09-19 19:49 ` [discuss] " Andi Kleen
2005-09-20 18:59 ` john stultz
2005-09-21 4:03 ` Daniel Jacobowitz
2005-09-21 15:15 ` Ray Bryant
2005-09-21 15:04 ` Andi Kleen
2005-09-21 15:46 ` Ray Bryant
2005-09-22 8:00 ` Jonas Oreland
2005-09-21 20:17 ` Andrew Morton
2005-10-07 12:26 ` Vladimir B. Savkin
2005-10-07 12:31 ` Andi Kleen
2005-10-07 14:15 ` Vladimir B. Savkin
2005-10-07 14:21 ` [discuss] " Velu Erwan
2005-10-08 10:11 ` Vladimir B. Savkin
2005-10-10 18:03 ` john stultz
2005-10-10 18:12 ` Vladimir B. Savkin
2005-10-10 18:19 ` Jonas Oreland
2005-10-11 7:35 ` Vladimir B. Savkin
2005-10-11 8:06 ` Andi Kleen
2005-10-11 16:27 ` Jonas Oreland [this message]
2005-10-25 7:35 ` x86-64: Syncing dualcore cpus TSCs Jonas Oreland
2005-10-25 7:42 ` Andi Kleen
2005-10-26 0:05 ` David Lang
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=434BE7E9.8000501@mysql.com \
--to=jonas@mysql.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=master@sectorb.msk.ru \
/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.