linux-kernel - Re: [RCF PATCH] genirq/debugfs: Triggering of interrupts from userspace

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: <4adc52d6-b7f6-a992-cd67-ba112edc1d01@arm.com>
Date:   Wed, 16 Aug 2017 15:58:04 +0100
From:   Marc Zyngier <marc.zyngier@....com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [RCF PATCH] genirq/debugfs: Triggering of interrupts from
 userspace

On 16/08/17 15:50, Thomas Gleixner wrote:
> On Thu, 20 Jul 2017, Marc Zyngier wrote:
>> When developing new (and therefore buggy) interrupt related
>> code, it can sometimes be useful to inject interrupts without
>> having to rely on a device to actually generate them.
>>
>> This functionnality relies on the irqchip driver to expose
>> a irq_set_irqchip_state(IRQCHIP_STATE_PENDING) callback.
> 
> I like that, but can we please extend that to utilize the irq resend
> mechanism:
> 
> 	desc = ....;
> 
> 	chip_bus_lock(desc);
>         raw_spin_lock_irq(&desc->lock);
> 
> 	if (has_set_state(desc))
> 		set_state(desc);
> 	else
> 		check_irq_resend(desc);
> 
> or something to that effect?
Definitely. That'd allow more HW to be supported. I'll have a look.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...