From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm-46 release Date: Sat, 13 Oct 2007 09:13:32 +0200 Message-ID: <4710701C.2040200@qumranet.com> References: <470C8D28.2060408@qumranet.com> <470F2806.8090902@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Gerd Hoffmann Return-path: In-Reply-To: <470F2806.8090902-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Gerd Hoffmann wrote: > Avi Kivity wrote: > >> We've now switched to allocating guest memory in userspace rather than >> in the kernel. >> > > Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to > use that. If I want to back vm memory with a file mapping, how can I do > that? > kvmctl.h doesn't expose an API for that currently, though is should be fairly trivial to do so. The kernel API is straightforward: take this bunch of memory and present it to a guest at some address. The kernel doesn't care if the memory came from a file mmap() or some other source. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/