All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: announce: PPSkit patch for Linux 2.4.2 (pre6)
Date: Wed, 11 Apr 2001 11:18:09 -0700	[thread overview]
Message-ID: <3AD49FE1.D609E032@transmeta.com> (raw)
In-Reply-To: <E14nOy5-0007Ei-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > appropriately.)  One could, at least theoretically, make them usable
> > in kernel space only (in user space there is no hope, since you can't
> > know which CPU's TSC you're reading), but these machines seem to be so
> > rare that hardly anyone technical enough to fix it cares.
> 
> Im working on making the 'notsc' automatic. Trying to 'fix' it is just plain
> hard work. With the fixed one however we can still use the tsc for udelay
> as we have per cpu loops_per_jiffy data.
> 
> This btw is why -ac figures out the bus multiplier on your processors. If they
> dont match then we know tsc wants to be off. Just nobody has written the code
> to disable it across all CPUs yet
> 

Yes, there are two cases where we can "fix" it: in the timer interrupt
code, and the loops_per_jiffy stuff.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

      reply	other threads:[~2001-04-11 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0104091815160.1367-300000@terran.bussi.de>
     [not found] ` <3AC83FF1.27420.398B86@localhost>
2001-04-10  7:12   ` announce: PPSkit patch for Linux 2.4.2 (pre6) Ulrich Windl
2001-04-11 17:56     ` H. Peter Anvin
2001-04-11 18:03       ` Alan Cox
2001-04-11 18:18         ` H. Peter Anvin [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=3AD49FE1.D609E032@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.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 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.