public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Len Brown <lenb@kernel.org>
Cc: Andi Kleen <ak@suse.de>, linux-acpi@vger.kernel.org
Subject: Re: [patch] ACPI: Keep TSC stable, when lapic_timer_c2_ok is set
Date: Thu, 10 May 2007 22:50:56 +0200	[thread overview]
Message-ID: <1178830256.22481.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200705100409.37753.lenb@kernel.org>

> Note, however, that the assumption that the TSC and the LAPIC
> timer breaking under the same conditions will not always
> be true going forward.
> 
> In particular, there will be systems with a fully functional TSC
> and a broken LAPIC timer.  But I guess we'll cross that bridge
> when we come to it...

Sigh, is there any kind of breakage which is not invented yet ?

I guess we need to have a seperate option for the TSC vs. C2 then.

	tglx



      reply	other threads:[~2007-05-10 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 16:33 [patch] ACPI: Keep TSC stable, when lapic_timer_c2_ok is set Thomas Gleixner
2007-05-10  8:09 ` Len Brown
2007-05-10 20:50   ` Thomas Gleixner [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=1178830256.22481.1.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=ak@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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