| 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
| ||
|
Message-Id: <1170791739.3455.3.camel@dwalker1> Date: Tue, 06 Feb 2007 11:55:39 -0800 From: Daniel Walker <dwalker@...sta.com> To: Thomas Gleixner <tglx@...utronix.de> Cc: Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org, mingo@...e.hu Subject: Re: 2.6.20-rc6-mm3 On Tue, 2007-02-06 at 20:07 +0100, Thomas Gleixner wrote: > On Tue, 2007-02-06 at 10:45 -0800, Daniel Walker wrote: > > > > -rt tree also .. I haven't done a bisect , but I'm assuming this is HRT > > > > related .. > > > > > > And why should it increment ? Is there a rule that it has to ? > > > > I don't know .. I would imagine some users might look at it and wonder > > why there timer isn't ticking (I know it actually is ticking , but they > > don't), when it has is every other kernel. > > What kind of artificial problem are you creating here ? I'm not trying to create anything .. However, as I said before the /proc/interrupts "timer" entry doesn't work the same as it has in other kernels. If you think that isn't a problem then explain why .. > > We could just remove the timer entry . > > No we can't. The timer interrupt is setup and it does not go away, as we > keep the PIT as a backup for the broken lapics. Ok, how about adding the interrupts to the list which are driving the timer ? Daniel - 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/
Powered by blists - more mailing lists