[Top] [All Lists]

Re: implementation of software suspend on MIPS. (system log)

To: Hyon Lim <>
Subject: Re: implementation of software suspend on MIPS. (system log)
From: "J. Scott Kasten" <>
Date: Thu, 1 Nov 2007 11:00:20 -0400 (EDT)
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=Received:X-YMail-OSG:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To:Message-ID:References:MIME-Version:Content-Type; b=EBFOrolZBocMn8McaG2ExegTffcjMVjPQ8yBhoOmjp+5S/VW/ezO8OJJDXdTppj3OrFrjZa5YzAtflIQT1lRiexg0WrMZz8Jh40oFrASs6zrzsafCtqaV8VLfNeXToPDnxSQV3lrrmg8kW2o1OSfo2R25PpJ6Lg/sIoYzYgh7xI= ;
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <>

On Thu, 1 Nov 2007, Hyon Lim wrote:

Thank you for comments.
The remain work of my software suspend on MIPS project is resume procedure.
I already confirmed that suspend function was work. (See my post which
contains system log).

In an i386 implementation, there are only few assembly code for suspend and
resume procedure.
(You can refer :
So, my work will be similar with i386 implementation. Assembly code used in
i386 implementation are several processor context related job
and copy saved page to memory. Instruction used in my MIPS implementation
will be compatible to most of MIPS processor.
Because the instruction used in implementation is very basic (store and load
and branch).

I agree your opinion related to maintainability and readability. So I
implement my work with C and few assembly code.
Thank you for advice.

I look forward to your eventual success. :)

<Prev in Thread] Current Thread [Next in Thread>