linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Thomas Gleixner <tglx@timesys.com>
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, 30 Jun 2006 23:09:22 +0200	[thread overview]
Message-ID: <20060630210922.GA1717@elf.ucw.cz> (raw)
In-Reply-To: <1151694950.25491.757.camel@localhost.localdomain>

Hi!

> > > > I briefly tested -dyntick5 on my thinkpad, and it seems to work
> > > > okay... but timer still seems to tick at 250Hz.
> > > 
> > > > ...am I doing something wrong?
> > > 
> > > can you send me the bootlog and your .config file please ?
> > 
> > ...attached. (I do not have to enable anything in sysfs/commandline to
> > enable noidlehz, right?).
> 
> Right. 
> 
> You trapped into the no apic on SMP trap. I did not come around to fix
> that yet. What happens that you don't have lapic on the commandline and
> BIOS has lapic disabled. Therefor Linux switches to IPI broadcasting if
> the PIT interrupt, which does not work with idle_hz and highres timer as
> those are per cpu. I will fix that for SMP kernels which bring up only
> one CPU.
> 
> You can work around that for now by either using an UP kernel or
> enabling local APIC, which is recommended anyway because the APIC timer
> is faster to access and has longer max time than PIT.

Thanks, it works okay with UP kernel.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-06-30 21:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 20:06 [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ -V4 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 [this message]
     [not found] <fa.lKfxxA+pCJb5tSZbL1XnnrPzaeQ@ifi.uio.no>
2006-06-23  3:31 ` Robert Hancock
2006-06-23  8:27   ` Thomas Gleixner
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

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=20060630210922.GA1717@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    --cc=tglx@timesys.com \
    /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).