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
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_X86_TSC_DISABLE question
Date: Thu, 02 Jan 2003 10:36:17 -0800	[thread overview]
Message-ID: <344570000.1041532576@flay> (raw)
In-Reply-To: <20030102175740.GA13389@pusa.informat.uv.es>

> Is there a way to verify this? or must I contact the motherboard maker and
> ask for it? how I should ask it?

I'd just assume that it works unless you have > 4 CPUs. Boxes (like mine)
where it doesn't work tend to be arcane NUMA things with large CPU counts.

M.


  reply	other threads:[~2003-01-02 18:34 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
2003-01-02 17:57   ` uaca
2003-01-02 18:36     ` Martin J. Bligh [this message]
  -- 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=344570000.1041532576@flay \
    --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