Date: Tue, 9 Oct 2001 16:22:54 -0700 (PDT)
From: Castor Fu <castor@3pardata.com>
To: "Matt D. Robinson" <yakker@alacritech.com>
cc: Suparna Bhattacharya <suparna@in.ibm.com>, <lkcd@oss.sgi.com>
Subject: Re: Dump driver interface
In-Reply-To: <3BC38569.61E9B580@alacritech.com>
Message-ID: <Pine.LNX.4.33.0110091614470.24559-100000@marais>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk

On Tue, 9 Oct 2001, Matt D. Robinson wrote:

> In what sense?  Right now, we're a module, but I suspect you aren't referring
> to this.
>
> > This would imply factoring out the iteration through pages of memory and
> > device write routines.  In this case, various linux kernel parameters
> > might also not be available.
>
> Are you referring to something like LinuxBIOS?  Just curious.  We have
> briefly discussed something like this, along with putting in MCL's code.

Well, not LinuxBIOS, but yes, from a custom BIOS.  With things like the SMI
interrupt one could potentially get at a pretty wedged system from a BIOS.

Another factor to consider, (pardon my unfamiliarity with Linux and its
VM system), is that it looks like a single virtual memory address is associated
with each page in the dump file.  It doesn't seem like one could easily access
all user pages, because pages from different tasks would have the same address.

Is this address somehow unique in the mem_map table?

    -castor