public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: uaca@alumni.uv.es
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_X86_TSC_DISABLE question
Date: Mon, 6 Jan 2003 17:22:17 +0100	[thread overview]
Message-ID: <20030106162217.GC10554@pusa.informat.uv.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0301031800370.29107-100000@coffee.psychology.mcmaster.ca>

On Fri, Jan 03, 2003 at 06:01:13PM -0500, Mark Hahn wrote:
> > I think that CONFIG_X86_TSC_DISABLE should be more informative on this
> 
> at most, it should say "don't worry about this unless you need to.
> and you'll know it if you need to".


And It should say that the kernel test TSCs are syncroniced across CPUS at
boot time, which I've just have found:

The message is the following in a 2.4.19-pre6 kernel

checking TSC synchronization across CPUs: passed.


I hope this helps somebody


	Ulisses

                Debian GNU/Linux: a dream come true
-----------------------------------------------------------------------------
"Computers are useless. They can only give answers."            Pablo Picasso

--->	Visita http://www.valux.org/ para saber acerca de la	<---
--->	Asociación Valenciana de Usuarios de Linux		<---
 

  parent reply	other threads:[~2003-01-06 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 22:58 CONFIG_X86_TSC_DISABLE question uaca
     [not found] ` <Pine.LNX.4.44.0301031800370.29107-100000@coffee.psychology.mcmaster.ca>
2003-01-06 16:22   ` uaca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-02 14:44 uaca
2003-01-02 17:39 ` Martin J. Bligh
2003-01-02 17:57   ` uaca
2003-01-02 18:36     ` Martin J. Bligh

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=20030106162217.GC10554@pusa.informat.uv.es \
    --to=uaca@alumni.uv.es \
    --cc=hahn@physics.mcmaster.ca \
    --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