linux-kernel - Re: Clockevents: one-shoot mode is never enabled if local apic timer is disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1175509780.28263.107.camel@localhost.localdomain>
Date:	Mon, 02 Apr 2007 12:29:40 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Maxim Levitsky <maximlevitsky@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Clockevents: one-shoot mode is never enabled if local apic
	timer is disabled

On Mon, 2007-04-02 at 13:23 +0300, Maxim Levitsky wrote:
> Hi, 
> 
> Fortunately on my system lapic timer works.
> But then tick_broadcast_switch_to_oneshot is redundant, isn't it? 

No, it's necessary for the systems where the local APIC timer stops in
C3(C2), as we do not know this at the point where we setup the local
APIC. 

	tglx



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/