public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@timesys.com>,
	LKML <linux-kernel@vger.kernel.org>,
	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 08:17:24 -0600	[thread overview]
Message-ID: <449BF7F4.9080408@shaw.ca> (raw)
In-Reply-To: <20060623082609.GB1040@elte.hu>

Ingo Molnar wrote:
> * Thomas Gleixner <tglx@timesys.com> wrote:
> 
>>> 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.
> 
> hm, we should update the message to be less cryptic. Something like:
> 
>   'Disabling NO_HZ and high resolution timers due to no APIC'
> 
> and in this particular case we should also finetune the condition a bit 
> and make it conditional on the number of CPUs. I.e. if someone boots an 
> SMP kernel on a UP box we should still allow the PIT. (there wont be any 
> broadcasting done) [the only exception would be if CONFIG_HOTPLUG_CPU is 
> specified - in that case we cannot be sure whether a new CPU will be 
> plugged in or not]

Yes, I would say that this case should be handled better, considering 
this configuration is the default one for Fedora kernels, for one..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


  reply	other threads:[~2006-06-23 14:17 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
2006-06-23  8:26     ` Ingo Molnar
2006-06-23 14:17       ` Robert Hancock [this message]
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=449BF7F4.9080408@shaw.ca \
    --to=hancockr@shaw.ca \
    --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