From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 4 Nov 2002 11:46:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 4 Nov 2002 11:46:30 -0500 Received: from ns.suse.de ([213.95.15.193]:18962 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Mon, 4 Nov 2002 11:46:28 -0500 To: Alan Cox Cc: linux-kernel@vger.kernel.org Subject: Re: [lkcd-general] Re: What's left over. References: <1036429035.1718.99.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel> From: Andi Kleen Date: 04 Nov 2002 17:53:02 +0100 In-Reply-To: Alan Cox's message of "4 Nov 2002 17:39:41 +0100" Message-ID: X-Mailer: Gnus v5.7/Emacs 20.6 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alan Cox writes: > Let me ask another question here > > Other than "register_reboot_notifier()" and adding a > "register_exception_notifier()" chain what else does a dump tool need. > Register_exception_notifier seems to solve about 90% of the insmod gdb > problem space as well ? A memory dumper needs some infrastructure to find out what page is ram and what is hole etc. Basically an iterate_over_memmap_and_give_me_type() function. -Andi