From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259 Date: Mon, 05 Dec 2011 12:01:36 +0200 Message-ID: <4EDC9680.2070305@redhat.com> References: <4EDB762C.7090909@redhat.com> <4EDB78DE.6000109@web.de> <4EDB7A74.4060804@redhat.com> <4EDB7ADC.50906@web.de> <4EDB7DE2.2050301@redhat.com> <4EDB7E62.7090909@web.de> <4EDB8DDE.5040402@redhat.com> <4EDB8F7C.1070602@web.de> <4EDBA15E.3060309@redhat.com> <4EDBE865.6000907@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Blue Swirl , Marcelo Tosatti , kvm@vger.kernel.org, qemu-devel , Anthony Liguori , "Michael S. Tsirkin" To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:12652 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754320Ab1LEKCl (ORCPT ); Mon, 5 Dec 2011 05:02:41 -0500 In-Reply-To: <4EDBE865.6000907@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 12/04/2011 11:38 PM, Jan Kiszka wrote: > > > > It should be also possible to migrate from non-KVM device to KVM > > version, different names would prevent that for ever. > > It is (theoretically) possible with these patches as the vmstate names > are the same. KVM to TCG migration does not work right now, so I was > only able to test in-kernel <-> user space irqchip model migrations. btw, for the next-gen migration protocol, we'd probably be using QOM paths, not vmstate names; the QOM paths would include the device name? -- error compiling committee.c: too many arguments to function