From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] MMIO: Make coalesced mmio use a device per zone Date: Wed, 20 Jul 2011 10:55:36 +0200 Message-ID: <4E269808.7050606@siemens.com> References: <1311063011-4430-1-git-send-email-levinsasha928@gmail.com> <4E2544F3.9030203@redhat.com> <1311069182.9174.1.camel@lappy> <4E255584.1030003@redhat.com> <1311070673.9174.4.camel@lappy> <4E255D44.8000107@redhat.com> <4E25BB6B.90907@siemens.com> <4E25BC46.1040200@redhat.com> <4E25BD8D.1030509@siemens.com> <4E2690B5.9050206@redhat.com> <4E26954B.6000606@siemens.com> <4E26975C.1090402@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Sasha Levin , "kvm@vger.kernel.org" , Marcelo Tosatti To: Avi Kivity Return-path: Received: from thoth.sbs.de ([192.35.17.2]:18839 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745Ab1GTIzk (ORCPT ); Wed, 20 Jul 2011 04:55:40 -0400 In-Reply-To: <4E26975C.1090402@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-07-20 10:52, Avi Kivity wrote: > On 07/20/2011 11:43 AM, Jan Kiszka wrote: >>> >>> How do you implement this 3a, if your consumers are outside the main >>> process? I guess you could have an additional synchonize API (for >>> in-kernel consumers) or RPC (for external process consumers), but then >>> this is no longer a simple API. >> >> I'm not planning to leave the hypervisor process for now, not to speak >> of in-kernel models. Already for many other reasons, a synchronization >> API between a hypothetical decoupled device model and the core will be >> quite complex. The first step is to get it scalable using a single process. > > If we design a new kvm API, we must look a little more into the future > than satisfying immediate needs. That's true, but synchronization requirements are widely unrelated to this API and will have to by satisfied generically anyway. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux