From owner-freebsd-arch@FreeBSD.ORG Thu Jun 16 13:22:57 2005 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E3DD16A41C for ; Thu, 16 Jun 2005 13:22:57 +0000 (GMT) (envelope-from howardsue@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA10643D48 for ; Thu, 16 Jun 2005 13:22:56 +0000 (GMT) (envelope-from howardsue@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so288555wri for ; Thu, 16 Jun 2005 06:22:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nk3euspW0LqiuP2AIgwBgVSpCyhDsV7mOqsp2XIeF+fjp9PrUE+BZaz7opRX4NbATVoW1LlLnz+W+DkAXvZBQ6nnOqfuilxLmnq8G5vJ4lGjZzAiPQ7yemQFXhgL/tBN+B/ZtHD6WMa4SY8pBR4zcNOMfIs1DUP2QDl/emBPWps= Received: by 10.54.53.15 with SMTP id b15mr463608wra; Thu, 16 Jun 2005 06:22:56 -0700 (PDT) Received: by 10.54.124.4 with HTTP; Thu, 16 Jun 2005 06:22:56 -0700 (PDT) Message-ID: <1e89cd51050616062241e9e201@mail.gmail.com> Date: Thu, 16 Jun 2005 21:22:56 +0800 From: Sue Howard To: arch@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Kernel Dump X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sue Howard List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 13:22:57 -0000 Hi, I find there are three states of kernel dump support currently. 1. ARM and PowerPC.=20 Not supported yet. 2. I386, AMD64, Alpha.=20 The dump file contains dump header plus the raw physical memory image. The code in dump_machdep.c is almost same. 3. IA64, SPARC The dump file has private header besides dump header and raw physical memory image. The code is ready for importing a MI dump interface. I want to understand what IA64 and SPARC are different than i386. What is the private header is for? Is it tech problem or historic problem? Is it possible to remove the private header in order to make IA64 and SPARC share the dump code of i386? In my understanding, it should be possible. Since /dev/mem should be a physic memory image. Howard