linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@timesys.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@osdl.org>, Con Kolivas <kernel@kolivas.org>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ -V4
Date: Fri, 23 Jun 2006 10:27:18 +0200	[thread overview]
Message-ID: <1151051238.25491.223.camel@localhost.localdomain> (raw)
In-Reply-To: <449B60A9.2000809@shaw.ca>

On Thu, 2006-06-22 at 21:31 -0600, Robert Hancock wrote:
> Thomas Gleixner wrote:
> > An updated patchset is available from:
> > 
> > http://www.tglx.de/projects/hrtimers/2.6.17/patch-2.6.17-hrt-dyntick4.patch
> 
> On my Compaq Presario X1050 laptop running Fedora Core 5 I get:
> 
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> 
> Not sure exactly what this is indicating or what's triggered this, but 
> I'm assuming the patch isn't doing much on this machine?

The system is configured for SMP, but this is an UP machine and the APIC
is disabled in the BIOS. Linux uses then the PIT and an IPI mechanism to
broadcast timer events. We need to do the event reprogramming per CPU,
so we switch off in that situation.

Solution: Either use an UP kernel, or enable Local APIC in the BIOS (is
not possible in most BIOSes), or add "lapic" to the kernel command line.

Also for an UP kernel adding "lapic" to the commandline is good, as the
APIC is faster accessible than the PIT.

	tglx



  reply	other threads:[~2006-06-23  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.lKfxxA+pCJb5tSZbL1XnnrPzaeQ@ifi.uio.no>
2006-06-23  3:31 ` [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ -V4 Robert Hancock
2006-06-23  8:27   ` Thomas Gleixner [this message]
2006-06-23  8:26     ` Ingo Molnar
2006-06-23 14:17       ` Robert Hancock
2006-06-24  0:51     ` Robert Hancock
2006-06-24  1:09       ` Con Kolivas
2006-06-24  1:15         ` Con Kolivas
2006-06-19 20:06 Thomas Gleixner
2006-06-20 14:51 ` Michal Piotrowski
2006-06-29 17:48 ` Pavel Machek
2006-06-29 19:03   ` Thomas Gleixner
2006-06-30 18:07     ` Pavel Machek
2006-06-30 19:15       ` Thomas Gleixner
2006-06-30 21:09         ` Pavel Machek

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=1151051238.25491.223.camel@localhost.localdomain \
    --to=tglx@timesys.com \
    --cc=akpm@osdl.org \
    --cc=hancockr@shaw.ca \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    /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).