public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: uaca@alumni.uv.es,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_X86_TSC_DISABLE question
Date: Thu, 02 Jan 2003 09:39:40 -0800	[thread overview]
Message-ID: <124500000.1041529180@titus> (raw)
In-Reply-To: <20030102144409.GB8309@pusa.informat.uv.es>

Depends on your box. Most standard SMP boxes are all clocked off the
same clock, so it's not an issue.

--On Thursday, January 02, 2003 15:44:09 +0100 uaca@alumni.uv.es wrote:

> Hi all
>
> I would like to know if in wich degree the issue of unsynced TSCs also
> applies  on x86 SMP.
>
> Thanks
>
> 	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		<---
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>



  reply	other threads:[~2003-01-02 17:31 UTC|newest]

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

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=124500000.1041529180@titus \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uaca@alumni.uv.es \
    /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