From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] physical memory allocation?
Date: Tue, 9 Sep 2008 13:04:56 +0100 [thread overview]
Message-ID: <200809091304.58624.paul@codesourcery.com> (raw)
In-Reply-To: <48C63DBD.8040605@redhat.com>
> How about doing that *unconditionally*, not just for kqemu?
Unless you actually need it (qemu doesn't, and kqemu shouldn't) it just slows
things down, and breaks things when /dev/shm isn't big enough.
Paul
prev parent reply other threads:[~2008-09-09 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 9:11 [Qemu-devel] physical memory allocation? Gerd Hoffmann
2008-09-09 12:04 ` Paul Brook [this message]
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=200809091304.58624.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=kraxel@redhat.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.