mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <petkov@uni-muenster.de>
To: john stultz <johnstul@us.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pmtmr and PRINTK_TIME timings display
Date: Tue, 16 Aug 2005 10:35:30 +0200	[thread overview]
Message-ID: <200508161035.31085.petkov@uni-muenster.de> (raw)
In-Reply-To: <1124144326.8630.9.camel@cog.beaverton.ibm.com>

On Tuesday 16 August 2005 00:18, john stultz wrote:
> On Thu, 2005-08-04 at 17:23 +0200, Borislav Petkov wrote:
> > I get it. Actually, I wasn't very sure whether this is the right solution
> > since my desktop machine uses tsc timer as default while the laptop the
> > pmtmr. I also remember that there was a patch a while ago on lkml which
> > enabled a modifiable behavior for PRINTK_TIME through a /proc interface
> > and kernel boot option but it somehow didn't get accepted. Ok, then,
> > since we keep the jiffies solution across arch's, how can I force the
> > kernel to use tsc for printk timings so that i can see the deltas between
> > the different printk's instead of the jiffies_64 ns value? The Pentium-M
> > Centrino on the laptop evidently supports rdtsc as a msr instruction.
>
> The issue is that there are a number of laptops that do not properly
> support cpufreq and additionally newer laptop chips halt their TSC's
> when they go into C3 mode. This keeps the TSC from working as a proper
> timesource on these systems, and causes the need for alternative
> timesources like the ACPI PM timer.

This _is_ actually my laptop I'm testing it on and sofar no problem. But as 
Steven pointed out earlier, one probably needs a different kind of timing 
information besides delta timings. Besides, <scripts/show_delta> can do all 
the formatting and delta computation already.

Thanks & regards,
Borislav Petkov.

  reply	other threads:[~2005-08-16  8:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 12:59 Borislav Petkov
2005-08-04 13:19 ` Steven Rostedt
2005-08-04 15:23   ` Borislav Petkov
2005-08-04 15:44     ` Steven Rostedt
2005-08-15 22:18     ` john stultz
2005-08-16  8:35       ` Borislav Petkov [this message]
2005-08-15 22:14 ` john stultz

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=200508161035.31085.petkov@uni-muenster.de \
    --to=petkov@uni-muenster.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®