mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: hugh@veritas.com
Cc: macro@ds2.pg.gda.pl, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] setup.c notsc Re: Microsecond accuracy
Date: Wed, 13 Dec 2000 06:10:26 -0800 (PST)	[thread overview]
Message-ID: <2741.194.236.209.133.976716626.squirrel@www.zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012071856280.1138-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.21.0012071856280.1138-100000@localhost.localdomain>

> 
> The present situation is inconsistent: "notsc" removes cpuinfo's
> "tsc" flag in the UP case (when cpu_data[0] is boot_cpu_data), but
> not in the SMP case.  I don't believe HPA's recent mods affected that
> behaviour, but it is made consistent (cleared in SMP case too) by the
> patch I sent him a couple of days ago, below updated for test12-pre7...
> 

Great.  You've taken something that was somewhat broken in the UP case and 
introduced massive braindamage in the SMP case.  What really needs to be is 
that the global enables (boot_cpu_data) should be exposed.

    -hpa




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-13 15:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07 11:42 Kotsovinos Vangelis
2000-12-07 12:36 ` Tigran Aivazian
2000-12-07 14:13   ` Tigran Aivazian
2000-12-07 15:33     ` H. Peter Anvin
2000-12-07 16:07       ` Maciej W. Rozycki
2000-12-07 19:28         ` [PATCH] setup.c notsc " Hugh Dickins
2000-12-07 20:48           ` Maciej W. Rozycki
2000-12-13 14:10           ` H. Peter Anvin [this message]
2000-12-07 16:54 ` Christopher Friesen
2000-12-08  0:17   ` Kotsovinos Vangelis
2000-12-07 21:14 ` Karim Yaghmour
2000-12-08  0:18   ` Kotsovinos Vangelis

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=2741.194.236.209.133.976716626.squirrel@www.zytor.com \
    --to=hpa@zytor.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    /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

all inboxes | Powered by JetHome®