From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [RFC PATCH 0/8]: uninline & uninline Date: Sat, 23 Feb 2008 22:02:23 +0100 Message-ID: <20080223210223.GA12148@basil.nowhere.org> References: <1203515238-22848-1-git-send-email-ilpo.jarvinen@helsinki.fi> <20080223000220.e9229c99.akpm@linux-foundation.org> <20080223105517.4d706511.akpm@linux-foundation.org> <00ac01c87656$777c02a0$667407e0$@com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: 'Andrew Morton' , 'Andi Kleen' , 'Ilpo =?iso-8859-1?Q?J=E4rvinen'?= , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, 'David Miller' , 'Arnaldo Carvalho de Melo' To: Hua Zhong Return-path: Received: from smtp-out02.alice-dsl.net ([88.44.60.12]:45034 "EHLO smtp-out02.alice-dsl.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760063AbYBWVC0 (ORCPT ); Sat, 23 Feb 2008 16:02:26 -0500 Content-Disposition: inline In-Reply-To: <00ac01c87656$777c02a0$667407e0$@com> Sender: netdev-owner@vger.kernel.org List-ID: > Is it possible to catch this automatically, like, by re-defining > likely/unlikely to the raw form in specific file(s)? Sure it would be possible to define a IN_VDSO symbol in all vdso related files and then do that. Might be useful for other things too. vdso has some very specific requirements. -Andi