| 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: <20091126125659.GD1037@rakim.wolfsonmicro.main> Date: Thu, 26 Nov 2009 12:56:59 +0000 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Andy Walls <awalls@...ix.net> Cc: Tejun Heo <tj@...nel.org>, Peter Ujfalusi <peter.ujfalusi@...ia.com>, Stephen Rothwell <sfr@...b.auug.org.au>, "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Takashi Iwai <tiwai@...e.de> Subject: Re: linux-next: workqueues tree build failure On Thu, Nov 26, 2009 at 07:40:25AM -0500, Andy Walls wrote: > I'm not sure doing things like I2C transactions in the in the top half > of the IRQ handler is generally viable. On shared IRQ lines, wouldn't > this hold off the interrupt for another device for too long? You're going to need to do I2C I/O to acknowledge and deassert the interrupt on most of these devices so if someone's shared the IRQ line with something that's too latency sensitive the hardware is broken anyway. > Workhandlers for deferring work are a nice way to avoid such bad system > level interactions. In order to cope with the fact that the IRQ can't be deasserted without talking to the device it will almost always be masked while waiting for the deferred work. -- 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