Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761230Ab0FRNJ3 (ORCPT ); Fri, 18 Jun 2010 09:09:29 -0400 Received: from one.firstfloor.org ([213.235.205.2]:43709 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758315Ab0FRNJ2 (ORCPT ); Fri, 18 Jun 2010 09:09:28 -0400 Date: Fri, 18 Jun 2010 15:09:22 +0200 From: Andi Kleen To: Peter Zijlstra Cc: Andi Kleen , Huang Ying , Ingo Molnar , "H.PeterA" <"nvin hpa"@zytor.com>, linux-kernel@vger.kernel.org, Chris Mason Subject: Re: [RFC 1/3] Unified NMI delayed call mechanism Message-ID: <20100618130921.GC9045@basil.fritz.box> References: <1276334896-7075-1-git-send-email-ying.huang@intel.com> <1276862130.1875.7.camel@laptop> <20100618122532.GB9045@basil.fritz.box> <1276865304.1875.12.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1276865304.1875.12.camel@laptop> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 609 Lines: 15 > You generally want to pass more information along anyway, now your > callback function needs to go look for it. Much better to pass a > work_struct like thing around that is contained in the state it needs. But how would you allocate the work queue in an NMI? If it's only a single instance (like this bit) it can be always put into a per cpu variable. -Andi -- 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/