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: <20140313133707.GA24821@linutronix.de>
Date:	Thu, 13 Mar 2014 14:37:07 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Hans de Goede <hdegoede@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Carlo Caione <carlo.caione@...il.com>,
	Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH] irq: Add a new IRQF_ACK_BEFORE_UNMASK irq flag

* Thomas Gleixner | 2014-03-12 11:38:24 [+0100]:

>Untested patch below.

I assumed that I forgot that piece during backporting but infact it was
not part of the original patch.

--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -388,6 +388,7 @@ extern int no_irq_affinity;
  */
 extern void handle_level_irq(unsigned int irq, struct irq_desc *desc);
 extern void handle_fasteoi_irq(unsigned int irq, struct irq_desc *desc);
+extern void handle_fasteoi_late_irq(unsigned int irq, struct irq_desc *desc);
 extern void handle_edge_irq(unsigned int irq, struct irq_desc *desc);
 extern void handle_edge_eoi_irq(unsigned int irq, struct irq_desc *desc);
 extern void handle_simple_irq(unsigned int irq, struct irq_desc *desc);


One side note: Since we need to specify IRQCHIP_EOI_THREADED and
handle_fasteoi_late_irq() as the handler, would it be easily doable to use
the handle_fasteoi_irq() handler and skip the EOI in the threaded mode?
But if it creates a mess then leave it as it is.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ