From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35844) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBRK0-0006Qb-Li for qemu-devel@nongnu.org; Sun, 17 Apr 2011 08:43:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QBRJz-0001ki-U1 for qemu-devel@nongnu.org; Sun, 17 Apr 2011 08:43:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBRJz-0001ke-Ll for qemu-devel@nongnu.org; Sun, 17 Apr 2011 08:43:23 -0400 Message-ID: <4DAAE05F.5050902@redhat.com> Date: Sun, 17 Apr 2011 15:43:11 +0300 From: Avi Kivity MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Para-virtualized ram-based filesystem? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Ritchie, Stuart" Cc: "qemu-devel@nongnu.org" On 04/16/2011 02:58 AM, Ritchie, Stuart wrote: > > > >You can do this with ivshmem today. You give it a path to a shared > >memory file, and then there's a path in sysfs that you can mmap() in > >userspace in the guest. > > Please correct me if I am wrong, but with ivshmem you must to manage your > world within a single, fixed size region. I appreciate the simplicity of > mapping the whole region all in one go, but our requirements are a bit > different. Even if you could pass multiple -device ivshmem instances, > it's still a fixed environment. Right? > You could place a read-only filesystem (say iso9660) in the region and mount it; it will then appear as a complete filesystem. -- error compiling committee.c: too many arguments to function