From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1ISee5-0001MP-7C
	for qemu-devel@nongnu.org; Tue, 04 Sep 2007 16:05:09 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1ISee2-0001K4-1M
	for qemu-devel@nongnu.org; Tue, 04 Sep 2007 16:05:08 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1ISee1-0001K1-Sn
	for qemu-devel@nongnu.org; Tue, 04 Sep 2007 16:05:05 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1ISee1-0004UW-7Q
	for qemu-devel@nongnu.org; Tue, 04 Sep 2007 16:05:05 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: qemu device emulation libraries (was [PATCH]
	Patches from the PyQemu project)
Date: Tue, 4 Sep 2007 21:04:58 +0100
References: <1aa37d910709020650v7c491985r761886db64435ac0@mail.gmail.com>
	<1188852253.10151.3.camel@squirrel> <fbkcaq$l0b$1@sea.gmane.org>
In-Reply-To: <fbkcaq$l0b$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200709042104.59276.paul@codesourcery.com>
Reply-To: 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: qemu-devel@nongnu.org
Cc: Hollis Blanchard <hollisb@us.ibm.com>

> This could be very valuable when thinking about running qemu *on* embedded
> systems with constrained memory and processing power, which is exactly what
> the KVM for embedded PowerPC project is considering. In that scenario,
> being able to strip out all unnecessary functionality (especially
> including devices known to be irrelevant) becomes very important.

If you care about memory overhead the last thing you want is to be loading 
loads of bitty little shared libraries. You want to build a single binary 
with just the features you need.

Paul