mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] x86_64: warn if unable to configure apic main timer
Date: Thu, 23 Feb 2006 13:07:30 -0500	[thread overview]
Message-ID: <200602231310_MC3-1-B917-8A34@compuserve.com> (raw)

In-Reply-To: <200602231024.38599.ak@suse.de>

On Thu, 23 Feb 2006 at 10:24:38 +0100, Andi Kleen wrote:
> On Thursday 23 February 2006 10:17, Chuck Ebbert wrote:
> > When using the APIC main timer option on x86_64, sometimes it
> > fails to complete its setup.  Warn about this and suggest
> > the user try 'disable_timer_pin_1' if their system clock runs
> > too fast. Also, make printing of the exact result of APIC
> > timer calibration require 'apic=verbose'.
> 
> This is not the right solution. Have to find out what's going
> wrong and fix that.
> 

 I was thinking of this more as a band-aid for 2.6.16.

 But this patch is broken anyway; it will print the message on
non-bootstrap CPUs.

> I'm also experimenting with a different way to run the timer
> because apicmaintimer doesn't work on a lot of laptops
> because they have trouble running the APIC timer during c2.

 Yeah, I saw the Intel patch that does the exact opposite of
apicmaintimer.  It's kind of funny having both of them in there.

-- 
Chuck
"Equations are the Devil's sentences."  --Stephen Colbert


             reply	other threads:[~2006-02-23 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 18:07 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-23  9:17 Chuck Ebbert
2006-02-23  9:24 ` Andi Kleen

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=200602231310_MC3-1-B917-8A34@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®