linux-kernel - Re: genirq default

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]

Date:	Tue, 23 Jun 2009 18:31:41 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Pawel MOLL <pawel.moll@...com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: genirq default_disable()

On Tue, 23 Jun 2009, Pawel MOLL wrote:
> Folks,
> 
> A quick question about the interrupt management... (the story takes
> place in kernel/irq/chip.c ;-)
> 
> Here we have the default_enable():
> 
> static void default_enable(unsigned int irq)
> {
>         struct irq_desc *desc = irq_to_desc(irq);
> 
>         desc->chip->unmask(irq);
>         desc->status &= ~IRQ_MASKED;
> }
> 
> It calls chip->unmask(), which absolutely makes sense...
> 
> The default_disable(), however, is not symmetric:
> 
> static void default_disable(unsigned int irq)
> {
> }
> 
> Is there any reason why it shouldn't call chip->mask()?
> 
> I'll be more then happy to prepare a patch doing so, but maybe it's a
> feature not a bug and I'm just missing something?

Yup, it's a feature: delayed irq disable.

Disabling irqs on the hardware level can be expensive. So we keep them
enabled and mark the irq as disabled. When an interrupt comes in
during that time then we disable the irq on the hardware level for
real and note internaly that it happened. On enable we replay the
interrupt so nothing is lost. That replay can be in hardware or in
software.

Thanks,

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