From: "John R. Hogerhuis" <jhoger@pobox.com>
To: Antony T Curtis <antony.t.curtis@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [spam score 1/10 -pobox] Re: [Qemu-devel] Storing code caching
Date: Thu, 08 Jul 2004 11:42:33 -0700 [thread overview]
Message-ID: <1089312152.23205.1757.camel@aragorn> (raw)
In-Reply-To: <1089307504.59382.83.camel@pcgem.rdg.cyberkinetica.com>
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.
next prev parent reply other threads:[~2004-07-08 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 12:26 [Qemu-devel] Storing code caching Martin Williams
2004-07-08 17:05 ` John R. Hogerhuis
2004-07-08 17:25 ` Antony T Curtis
2004-07-08 18:42 ` John R. Hogerhuis [this message]
2004-07-08 19:42 ` Re[2]: " Igor Shmukler
2004-07-08 17:57 ` Martin Williams
2004-07-08 18:28 ` John R. Hogerhuis
2004-07-08 19:11 ` Julian Seward
2004-07-08 19:45 ` John R. Hogerhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089312152.23205.1757.camel@aragorn \
--to=jhoger@pobox.com \
--cc=antony.t.curtis@ntlworld.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.