| 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: <1368566144-13548-1-git-send-email-andreas.fenkart@streamunlimited.com>
Date: Tue, 14 May 2013 23:15:44 +0200
From: Andreas Fenkart <andreas.fenkart@...eamunlimited.com>
To: tglx@...utronix.de
Cc: linux-kernel@...r.kernel.org, rdunlap@...radead.org,
Andreas Fenkart <andreas.fenkart@...eamunlimited.com>
Subject: [RESEND][PATCH 1/1] genirq: outline lazy disable in kerneldoc of irq_disable function.
comment taken from changelog of d209a699a0b975ad
Signed-off-by: Andreas Fenkart <andreas.fenkart@...eamunlimited.com>
---
kernel/irq/chip.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index cbd97ce..ba1f076 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -213,6 +213,16 @@ void irq_enable(struct irq_desc *desc)
irq_state_clr_masked(desc);
}
+/**
+ * irq_disable - disable interrupt generation
+ * @desc: irq descriptor which should be disabled
+ *
+ * If the chip does not implement the irq_disable callback, we
+ * use a lazy disable approach. That means we mark the interrupt
+ * disabled, but leave the hardware unmasked. If an interrupt
+ * happens, then the interrupt flow handler masks the line at the
+ * hardware level and marks it pending.
+ */
void irq_disable(struct irq_desc *desc)
{
irq_state_set_disabled(desc);
--
1.7.10.4
--
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