linux-kernel - Re: NO_HZ: timer interrupt stuck

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070223.012519.48528691.davem@davemloft.net>
Date:	Fri, 23 Feb 2007 01:25:19 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	tglx@...utronix.de
Cc:	jengelh@...ux01.gwdg.de, kronos.it@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: NO_HZ: timer interrupt stuck

From: Thomas Gleixner <tglx@...utronix.de>
Date: Thu, 22 Feb 2007 18:39:19 +0100

> On Thu, 2007-02-22 at 09:26 -0800, David Miller wrote:
> > BTW, I'm adding support for sparc64, and before I get much further
> > will the code handle a oneshot-only device?  That's basically what I
> > have (sparc64 basically has a TSC and a "comparison" register, you
> > write the "comparison" register with the TSC value at which you'd like
> > the timer interrupt to occur, so it's one-shot and you have to write
> > it again to get the next timer).
> 
> Yes, all you need is to omit the CLOCK_EVT_FEAT_PERIODIC flag when you
> register your device.

Thanks a lot Thomas.

I noticed while doing this work that the generic clock code is
incompatible with the time interpolator, since both provide a
do_{get,set}timeofday() implementation.  Just FYI...
-
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/