linux-kernel - Re: HPET : timer routing setup with Legacy Routing Replacement bit set

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 for Android: free password hash cracker in your pocket

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

Message-ID: <p73ac4ljd6c.fsf@verdi.suse.de>
Date:	27 Sep 2006 21:56:59 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Om Narasimhan" <om.turyx@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: HPET : timer routing setup with Legacy Routing Replacement bit set

"Om Narasimhan" <om.turyx@...il.com> writes:

> Hi,
> I am working with a new bios for a server our company build. I am
> confused about the routing of the timer and arch/x86_64/kernel/time.c
> irq setup.
> 
> HPET specification states that if Legacy routing replacement enable
> bit is set, IRQ0 should not be connected to PIN0 of IOAPIC, and IRQ0
> should not generate any interrupts. But in the kernel code, timer is
> hard coded to irq0 (arch/x86_64/kernel/time.c : time_init(), calls
> setup_irq(0,&irq0). 0 being the irq number)
> 
> My question is, should it not be IRQ2 if HPET is enabled and Legacy
> Routing Replacement bit is enbaled?

Legacy Routing Replacement is currently not supported.

Feel free to contribute a patch supporting it though.

-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/