From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v5 4/5] Inter-VM shared memory PCI device Date: Wed, 12 May 2010 18:48:47 +0300 Message-ID: <4BEACDDF.20309@redhat.com> References: <1271872408-22842-1-git-send-email-cam@cs.ualberta.ca> <4BE90E6D.7070007@redhat.com> <4BE9572B.3010104@codemonkey.ws> <4BE963C9.9090308@redhat.com> <4BE96F50.1040506@redhat.com> <4BE97CE6.6000001@codemonkey.ws> <4BE98E4A.3010708@codemonkey.ws> <4BE99E32.3020507@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Cam Macdonell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:5231 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755029Ab0ELPs4 (ORCPT ); Wed, 12 May 2010 11:48:56 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 05/12/2010 06:32 PM, Cam Macdonell wrote: > >> We can tunnel its migration data through qemu. Of course, gathering its >> dirty bitmap will be interesting. DSM may be the way to go here (we can >> even live migrate qemu through DSM: share the guest address space and >> immediately start running on the destination node; the guest will fault its >> memory to the destination. An advantage is that that the cpu load is >> immediately transferred. >> >> > Given the potential need to develop DSM and migrating multiple VMs > simultaneously as well as few details to decide on, can the patch > series (with other review tweaks fixed) be accepted without migration > support? Definitely. I don't expect DSM to materialize tomorrow (or ever). -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.