Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752246AbZL1Qdu (ORCPT ); Mon, 28 Dec 2009 11:33:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751898AbZL1Qdt (ORCPT ); Mon, 28 Dec 2009 11:33:49 -0500 Received: from mail.windriver.com ([147.11.1.11]:40665 "EHLO mail.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751690AbZL1Qds (ORCPT ); Mon, 28 Dec 2009 11:33:48 -0500 Message-ID: <4B38DDC5.4080202@windriver.com> Date: Mon, 28 Dec 2009 10:33:09 -0600 From: Jason Wessel User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Peter Zijlstra CC: linux-kernel@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net, mingo@elte.hu, mort@sgi.com, linux-arch@vger.kernel.org Subject: Re: [PATCH 05/37] kdb: core for kgdb back end References: <1261603190-5036-1-git-send-email-jason.wessel@windriver.com> <1261603190-5036-2-git-send-email-jason.wessel@windriver.com> <1261603190-5036-3-git-send-email-jason.wessel@windriver.com> <1261603190-5036-4-git-send-email-jason.wessel@windriver.com> <1261603190-5036-5-git-send-email-jason.wessel@windriver.com> <1261603190-5036-6-git-send-email-jason.wessel@windriver.com> <1261652672.4937.189.camel@laptop> In-Reply-To: <1261652672.4937.189.camel@laptop> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Dec 2009 16:33:09.0721 (UTC) FILETIME=[7104D490:01CA87DB] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1638 Lines: 37 Peter Zijlstra wrote: > On Wed, 2009-12-23 at 15:19 -0600, Jason Wessel wrote: >> +kdb_prio(char *name, struct rt_prio_array *array, kdb_printf_t xxx_printf, [..] >> +kdb_runqueue(unsigned long cpu, kdb_printf_t xxx_printf) [..] > > So what is this code supposed to do? It looks like it simply cannot be > correct. > Beyond the fact that the code may not be right, it is a small part of a kdb module which is not included, and these functions can immediately disappear. For reference, the original kdb module was called "kdbm_sched" and I believe it was intended as an aid to help debug the scheduler and process priorities in earlier versions of the kernel. I have removed all this code and reduced the patch to kernel/sched.c to the following. The reason we need the attached patch is to be able to call curr_task() for kdb to perform some basic per cpu task analysis while the system is stopped. Thanks, Jason. --- a/kernel/sched.c +++ b/kernel/sched.c @@ -9784,9 +9784,9 @@ void normalize_rt_tasks(void) #endif /* CONFIG_MAGIC_SYSRQ */ -#ifdef CONFIG_IA64 +#if defined(CONFIG_IA64) || defined(CONFIG_KGDB_KDB) /* - * These functions are only useful for the IA64 MCA handling. + * These functions are only useful for the IA64 MCA handling, or kdb. * * They can only be called when the whole system has been * stopped - every CPU needs to be quiescent, and no scheduling -- 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/