linux-kernel - Re: Timer Selection

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: <a2ebde260609100723v553d3810o1651dc181e7db3bf@mail.gmail.com>
Date:	Sun, 10 Sep 2006 22:23:05 +0800
From:	"Dong Feng" <middle.fengdong@...il.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Timer Selection

Thank you very much.


2006/9/10, Andi Kleen <ak@...e.de>:
> On Sunday 10 September 2006 12:34, Dong Feng wrote:
> > In i386 architecture, there are five timers as candidates in the selection
> > of "cur_timer." I feel among the five only two types can be used as Kernel
> > base timer, HPET and PIT. Kernel base timer is the timer trigger
> > timer_interrupt() periodically. Namely, the timer installed on IRQ 0 in
> > i386 architecture.
> >
> > Is the above understanding correct? Particularly I want to confirm which
> > timers can be used as Kernel base timer.
>
> Only HPET and PIT can be interrupt 0 in the PC architecture
> (HPET only if the legacy option is available), but there is no reason
> the main timer handler cannot be driven from another interval timer (e.g.
> x86-64 offers the APIC timer as a option for this)
>
> -Andi
>
-
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/