From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764849AbXKTWne (ORCPT ); Tue, 20 Nov 2007 17:43:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760683AbXKTWnF (ORCPT ); Tue, 20 Nov 2007 17:43:05 -0500 Received: from dsl-mtryl-66-18-218-115-cgy.nucleus.com ([66.18.218.115]:62444 "HELO schaus.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1758888AbXKTWnE (ORCPT ); Tue, 20 Nov 2007 17:43:04 -0500 X-Greylist: delayed 419 seconds by postgrey-1.27 at vger.kernel.org; Tue, 20 Nov 2007 17:43:04 EST Message-ID: <47436152.8080509@schaus.ca> Date: Tue, 20 Nov 2007 15:36:02 -0700 From: Cameron Schaus User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: CONFIG_PROFILING on production system Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Is there a reason why I would not want to run a production system with CONFIG_PROFILING enabled? I am wondering if there are any reasons associated with performance, stability or security that I should worry about when CONFIG_PROFILING is enabled. Thanks, Cam