Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262120AbUK3PzX (ORCPT ); Tue, 30 Nov 2004 10:55:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262126AbUK3PzX (ORCPT ); Tue, 30 Nov 2004 10:55:23 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:15757 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S262120AbUK3PzS (ORCPT ); Tue, 30 Nov 2004 10:55:18 -0500 Date: Tue, 30 Nov 2004 16:55:10 +0100 (MET) From: Jan Engelhardt To: "Hanson, Jonathan M" cc: linux-kernel@vger.kernel.org Subject: Re: Walking all the physical memory in an x86 system In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 785 Lines: 23 > I've written a 2.4 kernel module where I'm trying to walk and >record all of the physical memory contents in an x86 system. I have the >following code fragment that does it but I suspect I'm missing a portion >of the memory: > >Is there a better way to record all of the contents of physical memory >since what I have above doesn't seem to get everything? Maybe something userspace based? dd_rescue /dev/mem copyofmem Jan Engelhardt -- Gesellschaft für Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 Göttingen, www.gwdg.de - 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/