From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753939Ab0DUKVR (ORCPT ); Wed, 21 Apr 2010 06:21:17 -0400 Received: from casper.infradead.org ([85.118.1.10]:53431 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753923Ab0DUKVO (ORCPT ); Wed, 21 Apr 2010 06:21:14 -0400 Subject: Re: pci_get_dev_by_id() from interrupt handlers From: Peter Zijlstra To: Joerg Roedel Cc: Greg KH , Joerg Roedel , Jesse Barnes , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20100421100528.GG31537@amd.com> References: <20100420160423.GD31537@amd.com> <20100420163215.GB3270@kroah.com> <20100420173552.GA15669@8bytes.org> <20100420175202.GA4874@kroah.com> <20100421100528.GG31537@amd.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 21 Apr 2010 12:21:11 +0200 Message-ID: <1271845271.1776.74.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2010-04-21 at 12:05 +0200, Joerg Roedel wrote: > > > Why not do the whole thing in an interrupt task as the whole thing > > sounds like something that shouldn't be done in interrupt context, > > right? Now that we have this type of functionality, we should take > > advantage of it :) > > Ok, I think I move the IOMMU interrupt handling to a tasklet. > tasklet is softirq context, and is not what gregkh was talking about. You'd still need to change the klist spinlock to be softirq-safe.