All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: dean gaudet <dean@arctic.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] All Transmeta CPUs have constant TSCs
Date: Mon, 08 Jan 2007 15:54:48 -0800	[thread overview]
Message-ID: <45A2D9C8.9020007@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701081506330.12282@twinlark.arctic.org>

dean gaudet wrote:
> On Mon, 8 Jan 2007, H. Peter Anvin wrote:
> 
>> I *definitely* support the concept that RDPMC 0 should could CPU cycles by
>> convention in Linux.
> 
> unfortunately that'd be very limiting and annoying on core2 processors 
> which have dedicated perf counters for clocks unhalted (actual vs. 
> nominal), but only 2 configurable perf counters.  i forget what ecx value 
> gets you the dedicated counters... but a solution which might work would 
> be a syscall to return the perf counter number...
> 
> or we could just merge perfmon ;)
> 

OK, if there are dedicated counters in hardware at a different number, 
we probably should make it an ELF entry value (no need to make it a 
syscall for a constant.)

	-hpa

      reply	other threads:[~2007-01-08 23:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05  1:48 [PATCH] All Transmeta CPUs have constant TSCs H. Peter Anvin
2007-01-05 14:25 ` Jan Engelhardt
2007-01-08  8:02   ` dean gaudet
2007-01-08 20:19     ` Jan Engelhardt
2007-01-08 20:51       ` Chris Friesen
2007-01-08 20:51       ` H. Peter Anvin
2007-01-08 23:13         ` dean gaudet
2007-01-08 23:54           ` 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=45A2D9C8.9020007@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@osdl.org \
    --cc=dean@arctic.org \
    --cc=jengelh@linux01.gwdg.de \
    --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.