Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752664Ab0FGV22 (ORCPT ); Mon, 7 Jun 2010 17:28:28 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:56606 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751670Ab0FGV21 convert rfc822-to-8bit (ORCPT ); Mon, 7 Jun 2010 17:28:27 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=cDKMo6pifomMpXUY49V1kvMIMDbk0a6pRfIwTUPIn+MF7EYxKpUVJAwYYy8OLdnqDm SCmIYchHumharhftSQtfPGi36pBalL1BKWnA6pM4K8yVxkDgRq6Aw9Blv9zENzVcZR0U jQQ0T+JweUosscgdUn6SaVHuZUGykaFDfIBZg= MIME-Version: 1.0 In-Reply-To: References: <1275686352.2970.2.camel@eha.doredevelopment.dk> <20100605151031.2d562268@hina.wild-wind.fr.eu.org> <1275914058.2818.8.camel@eha.doredevelopment.dk> Date: Mon, 7 Jun 2010 23:28:23 +0200 Message-ID: Subject: Re: [RFC][PATCH] irq: support IRQ_NESTED_THREAD with non-threaded interrupt handlers From: Esben Haabendal To: Thomas Gleixner Cc: Esben Haabendal , linuxppc-dev@ozlabs.org, Marc Zyngier , LKML , Ingo Molnar , joachim.eastwood@jotron.com, Peter Zijlstra , David Miller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1395 Lines: 34 On Mon, Jun 7, 2010 at 5:06 PM, Thomas Gleixner wrote: > Maybe you understand now, why I was pretty sure upfront, that your > approach was wrong even without knowing all the gory details ? :) I understand. There is a better solution, which is to use threaded interrupts where needed. But I must confess that I am disappointed that you still fail to see how the pca953x patch actually eliminates the need for serialization. But I don't think there is much point in going on about that. The phy driver should be rewritten to use a threaded handler, it will solve my particular problem. And in the meantime, I have been promised to get the phy interrupts ofloaded to real CPU interrupt lines :-) Oh, I still think that the disable_irq_nosync documentaiton is misleading. Functions that are allowed in a particular context should not call functions that are not allowed to be called in that context. But now I know :-) /Esben -- Esben Haabendal, Senior Software Consultant Dor?Development ApS, Ved Stranden 1, 9560 Hadsund, DK-Denmark Phone: +45 51 92 53 93, E-mail: eha@doredevelopment.dk WWW: http://www.doredevelopment.dk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/