From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33591) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQAyM-0008RC-JF for qemu-devel@nongnu.org; Thu, 11 Apr 2013 02:27:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQAyL-00065k-Jm for qemu-devel@nongnu.org; Thu, 11 Apr 2013 02:27:02 -0400 Received: from mail-bk0-x229.google.com ([2a00:1450:4008:c01::229]:61672) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQAyL-00065Z-Ch for qemu-devel@nongnu.org; Thu, 11 Apr 2013 02:27:01 -0400 Received: by mail-bk0-f41.google.com with SMTP id i18so623120bkv.0 for ; Wed, 10 Apr 2013 23:27:00 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <516657AC.1090408@redhat.com> Date: Thu, 11 Apr 2013 08:26:52 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1365632901-15470-1-git-send-email-mrhines@linux.vnet.ibm.com> <1365632901-15470-12-git-send-email-mrhines@linux.vnet.ibm.com> In-Reply-To: <1365632901-15470-12-git-send-email-mrhines@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH RDMA support v1: 11/13] send pc.ram over RDMA List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: mrhines@linux.vnet.ibm.com Cc: aliguori@us.ibm.com, mst@redhat.com, qemu-devel@nongnu.org, owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com, gokul@us.ibm.com Il 11/04/2013 00:28, mrhines@linux.vnet.ibm.com ha scritto: > > +#ifdef CONFIG_RDMA > +int qemu_rdma_registration_start(QEMUFile *f, void *opaque, uint32_t flags) > +{ > + DPRINTF("start section: %d\n", flags); > + qemu_put_be64(f, RAM_SAVE_FLAG_HOOK); > + return 0; > +} > +#endif > This must be in migration-rdma.c. Move RAM_SAVE_FLAG_HOOK to migration/migration.h with a comment like this: /* Whenever this is found in the data stream, the flags * will be passed to ram_load_hook in the incoming-migration * side. This lets before_ram_iterate/after_ram_iterate add * transport-specific sections to the RAM migration data. */ Paolo