linux-kernel - RE: [PATCH v1] x86/irq: handle chained interrupts during IRQ migration

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: <2FABAEF0D3DCAF4F9C9628D6E2F968451CE18C@BGSMSX102.gar.corp.intel.com>
Date:	Thu, 31 May 2012 07:36:19 +0000
From:	"Iyer, Sundar" <sundar.iyer@...el.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Van De Ven, Arjan" <arjan.van.de.ven@...el.com>,
	"Monroy, German" <german.monroy@...el.com>
Subject: RE: [PATCH v1] x86/irq: handle chained interrupts during IRQ
 migration

>-----Original Message-----
>From: Thomas Gleixner [mailto:tglx@...utronix.de]
>Sent: Thursday, May 31, 2012 1:01 PM
>>
>> Handle this by introducing a irq_is_chained() check which is based on
>> the IRQ_NOREQUEST flag being set for such interrupts. fixup_irq() can
>> then handle such interrupts and not skip them over.
>
>No, we need a separate flag for those. IRQ_NORREQUEST is not a reliable indicator.

I posted a v2 for this patch with all the flags; else will it be okay me adding
a new flag called IRQ_CHAINED and a new function similar to set_noprobe* helpers?

Cheers!
--
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/