linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Joerg Roedel" <joerg.roedel@amd.com>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] x86_64: fix cpu MHz reporting on constant_tsc cpus
Date: Fri, 16 Mar 2007 12:24:41 +0100	[thread overview]
Message-ID: <200703161224.42006.ak@suse.de> (raw)
In-Reply-To: <20070315165047.GY21463@amd.com>


>
> Yes. You are right. I will fix that and send a new version.  Thanks for
> the review.

I already fixed it up and fixed some other bugs. The changes to tsc_khz
in nmi.c were wrong because the performance counters don't tick 
at tsc frequency.

-Andi

      reply	other threads:[~2007-03-16 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13 10:00 [PATCH] x86_64: fix cpu MHz reporting on constant_tsc cpus Joerg Roedel
2007-03-14 23:01 ` [discuss] " Andi Kleen
2007-03-15 16:50   ` Joerg Roedel
2007-03-16 11:24     ` Andi Kleen [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=200703161224.42006.ak@suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=joerg.roedel@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).