From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [PATCH 0/4] Fastboot revisited: Asynchronous function calls Date: Sun, 4 Jan 2009 11:19:27 -0800 Message-ID: <20090104111927.1bed8269@infradead.org> References: <20090104092430.7ffd2c41@infradead.org> <20090104103104.6fdda9f2@infradead.org> <20090104110559.306186c4@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org To: Linus Torvalds Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, fweisbec@gmail.com, linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org, linux-acpi@vger.kernel.org, akpm@linux-foundation.org List-Id: linux-acpi@vger.kernel.org On Sun, 4 Jan 2009 11:11:53 -0800 (PST) Linus Torvalds wrote: > > > On Sun, 4 Jan 2009, Arjan van de Ven wrote: > > > > or we declare the irq probing stuff "rare" and just make THAT fully > > serializing.... > > do a full synchronization before starting a probe > > Yes. That's entirely possible. However, have you verified that if an > async thread does a synchronization, it doesn't deadlock? an async thread can synchronize on its own cookie. so yes if we make this a global serialize, we can't do irq autoprobing in async context. If we can use PNP/etc for serial.. I don't think that's a big deal.. nobody with sane hw would need to autoprobe ever. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org