From: Thomas Gleixner <tglx@linutronix.de>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Clockevents: one-shoot mode is never enabled if local apic timer is disabled
Date: Mon, 02 Apr 2007 11:34:44 +0200 [thread overview]
Message-ID: <1175506484.28263.101.camel@localhost.localdomain> (raw)
In-Reply-To: <200704021157.03368.maximlevitsky@gmail.com>
Maxim,
can you please fix your mail client to do proper line wraps at 78
chars ?
On Mon, 2007-04-02 at 11:57 +0300, Maxim Levitsky wrote:
> Hi,
>
> I finally figured out why one-shoot mode is enabled on my system only
> and only if local apic is enabled.
You could have asked me :)
> I tried to remove this check and this resulted in hard lock-up during
> boot with nolapic_timer
> Maybe this was connected to the fact that this function is called on
> both cpus, and if one set a
> broadcasting device(HPET) to one shoot mode, second is still not aware
> of this.
>
> Is it a bug or feature ?
One shot mode - used for NO_HZ and HIGH_RES - requires a working per cpu
timer.
When you disable the lapic timers, then we register the lapic timers
just as dummy devices to utilize the broadcast mechanism. Otherwise the
second CPU would be not working at all. I decided not to enable
nohz/highres when we have no usable per cpu devices available.
So consider it a feature :)
tglx
next prev parent reply other threads:[~2007-04-02 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 8:57 Clockevents: one-shoot mode is never enabled if local apic timer is disabled Maxim Levitsky
2007-04-02 9:34 ` Thomas Gleixner [this message]
2007-04-02 10:23 ` Maxim Levitsky
2007-04-02 10:29 ` Thomas Gleixner
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=1175506484.28263.101.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.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