linux-kernel - Re: IRQ affinity notifiers vs RT

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: <524EF05E.4070402@linutronix.de>
Date:	Fri, 04 Oct 2013 18:44:14 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Ben Hutchings <bhutchings@...arflare.com>
CC:	Steven Rostedt <rostedt@...dmis.org>,
	"Alexandra N. Kossovsky" <Alexandra.Kossovsky@...etlabs.ru>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: IRQ affinity notifiers vs RT

On 10/01/2013 01:44 AM, Ben Hutchings wrote:
> Right, but it looks quite strange to have this thread just for a
> (probably) quite rare event.  Maybe some day someone will work out how
> to make Octeon's IRQ management less unusual and then you can use the
> simpler approach for RT...

We have three threads for some rare events by now if I count correctly.
That is
- mce check on x86 (mce_notify_helper_thread)
- this one
- clock_was_set_delayed() (pending)

So right now I am thinking about a workqueue for rare events because if
I keep doing this we end up with a bunch useless tasks for something
that might never occur.

> Ben.

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