From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BidsN-0005mM-Kw
	for qemu-devel@nongnu.org; Thu, 08 Jul 2004 14:44:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BidsL-0005lh-Uu
	for qemu-devel@nongnu.org; Thu, 08 Jul 2004 14:44:07 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BidsL-0005le-RA
	for qemu-devel@nongnu.org; Thu, 08 Jul 2004 14:44:05 -0400
Received: from [216.254.0.203] (helo=mail3.speakeasy.net)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.34) id 1BidqA-0001OE-0H
	for qemu-devel@nongnu.org; Thu, 08 Jul 2004 14:41:50 -0400
Subject: Re: [spam score 1/10 -pobox]  Re: [Qemu-devel] Storing code caching
From: "John R. Hogerhuis" <jhoger@pobox.com>
In-Reply-To: <1089307504.59382.83.camel@pcgem.rdg.cyberkinetica.com>
References: <F85D0A87-D0D9-11D8-B4E3-000A95B1EB4C@mac.com>
	<1089306349.12383.1723.camel@aragorn>
	<1089307504.59382.83.camel@pcgem.rdg.cyberkinetica.com>
Content-Type: text/plain
Message-Id: <1089312152.23205.1757.camel@aragorn>
Mime-Version: 1.0
Date: Thu, 08 Jul 2004 11:42:33 -0700
Content-Transfer-Encoding: 7bit
Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Antony T Curtis <antony.t.curtis@ntlworld.com>
Cc: qemu-devel@nongnu.org

On Thu, 2004-07-08 at 10:25, Antony T Curtis wrote:
> On Thu, 2004-07-08 at 18:05, John R. Hogerhuis wrote:
> > On Thu, 2004-07-08 at 05:26, Martin Williams wrote:
> > > Has anyone thought about trying to store the code caching on disk?
> > 
> > Are you talking about "save machine state" essentially "suspend/resume?"
> > That is certainly possible and I believe it has been discussed on the
> > list.
> 
> <snip>
> 
> I think a more interesting idea is to 'virtualize' the memory.... That
> is, we provide a means for a guest to request more physical memory and
> to be able to release that memory back to the host... Perhaps also some
> method in which the host can warn the guest of low memory situations so
> that the guest can be more aggressive on memory reclaiming.
> 

Hmm... you're trying to tell me something, aren't you? ;-)

You'll need to connect the dots for the feeble-minded like myself.

How does this relate to persisting translated code (or
save-machine-state)?

-- John.