From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory semantics? Date: Wed, 25 Jan 2012 14:15:03 +0200 Message-ID: <4F1FF247.80301@redhat.com> References: <4F1810AF.8010002@siemens.com> <20120119172802.GD11381@amt.cnet> <4F185535.1060908@siemens.com> <4F1FE9CE.5050401@redhat.com> <4F1FEE1F.8080907@siemens.com> <4F1FEFCA.2060907@redhat.com> <4F1FF13E.5090405@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , qemu-devel , kvm To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:14311 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752665Ab2AYMPM (ORCPT ); Wed, 25 Jan 2012 07:15:12 -0500 In-Reply-To: <4F1FF13E.5090405@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 01/25/2012 02:10 PM, Jan Kiszka wrote: > > > >> Would a machine option > >> "kvm_shadow_memory=n" be desirable? > > > > Not sure, this is a host option, not a guest option. Machine options > > should be guest-visible. > > machine options are not guest visible. Basically, this options falls > into the same category as kernel_irqchip. They should be. We should work hard to separate the guest ABI from everything else. Same as kvm-apic appearing in the qdev name. > Do we have alternatives? A top-level command line options is surely none. -kvm shadow-memory=n,... -accel kvm,shadow-memory=n,... -- error compiling committee.c: too many arguments to function