From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DBD9C43613 for ; Fri, 21 Jun 2019 00:52:52 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3E1602075E for ; Fri, 21 Jun 2019 00:52:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3E1602075E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:53674 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1he7nP-0001UM-8C for qemu-devel@archiver.kernel.org; Thu, 20 Jun 2019 20:52:51 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59292) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1he7kO-0008M0-Lc for qemu-devel@nongnu.org; Thu, 20 Jun 2019 20:49:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1he7Sc-0005iM-Eu for qemu-devel@nongnu.org; Thu, 20 Jun 2019 20:31:25 -0400 Received: from mga14.intel.com ([192.55.52.115]:63158) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1he7Sa-0005cV-TS for qemu-devel@nongnu.org; Thu, 20 Jun 2019 20:31:22 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jun 2019 17:31:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,398,1557212400"; d="scan'208";a="358713769" Received: from joy-optiplex-7040.sh.intel.com (HELO joy-OptiPlex-7040) ([10.239.13.9]) by fmsmga005.fm.intel.com with ESMTP; 20 Jun 2019 17:31:11 -0700 Date: Thu, 20 Jun 2019 20:25:18 -0400 From: Yan Zhao To: Kirti Wankhede Message-ID: <20190621002518.GF9303@joy-OptiPlex-7040> References: <1561041461-22326-1-git-send-email-kwankhede@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1561041461-22326-1-git-send-email-kwankhede@nvidia.com> User-Agent: Mutt/1.9.4 (2018-02-28) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 192.55.52.115 Subject: Re: [Qemu-devel] [PATCH v4 00/13] Add migration support for VFIO device X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Yan Zhao Cc: "Zhengxiao.zx@Alibaba-inc.com" , "Tian, Kevin" , "Liu, Yi L" , "cjia@nvidia.com" , "eskultet@redhat.com" , "Yang, Ziye" , "yulei.zhang@intel.com" , "cohuck@redhat.com" , "shuangtai.tst@alibaba-inc.com" , "dgilbert@redhat.com" , "Wang, Zhi A" , "mlevitsk@redhat.com" , "pasic@linux.ibm.com" , "aik@ozlabs.ru" , "alex.williamson@redhat.com" , "eauger@redhat.com" , "qemu-devel@nongnu.org" , "felipe@nutanix.com" , "jonathan.davies@nutanix.com" , "Liu, Changpeng" , "Ken.Xue@amd.com" Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Thu, Jun 20, 2019 at 10:37:28PM +0800, Kirti Wankhede wrote: > Add migration support for VFIO device > > This Patch set include patches as below: > - Define KABI for VFIO device for migration support. > - Added save and restore functions for PCI configuration space > - Generic migration functionality for VFIO device. > * This patch set adds functionality only for PCI devices, but can be > extended to other VFIO devices. > * Added all the basic functions required for pre-copy, stop-and-copy and > resume phases of migration. > * Added state change notifier and from that notifier function, VFIO > device's state changed is conveyed to VFIO device driver. > * During save setup phase and resume/load setup phase, migration region > is queried and is used to read/write VFIO device data. > * .save_live_pending and .save_live_iterate are implemented to use QEMU's > functionality of iteration during pre-copy phase. > * In .save_live_complete_precopy, that is in stop-and-copy phase, > iteration to read data from VFIO device driver is implemented till pending > bytes returned by driver are not zero. > * Added function to get dirty pages bitmap for the pages which are used by > driver. > - Add vfio_listerner_log_sync to mark dirty pages. > - Make VFIO PCI device migration capable. If migration region is not provided by > driver, migration is blocked. > > Below is the flow of state change for live migration where states in brackets > represent VM state, migration state and VFIO device state as: > (VM state, MIGRATION_STATUS, VFIO_DEVICE_STATE) > > Live migration save path: > QEMU normal running state > (RUNNING, _NONE, _RUNNING) > | > migrate_init spawns migration_thread. > (RUNNING, _SETUP, _RUNNING|_SAVING) > Migration thread then calls each device's .save_setup() > | > (RUNNING, _ACTIVE, _RUNNING|_SAVING) > If device is active, get pending bytes by .save_live_pending() > if pending bytes >= threshold_size, call save_live_iterate() > Data of VFIO device for pre-copy phase is copied. > Iterate till pending bytes converge and are less than threshold > | > On migration completion, vCPUs stops and calls .save_live_complete_precopy > for each active device. VFIO device is then transitioned in > _SAVING state. > (FINISH_MIGRATE, _DEVICE, _SAVING) > For VFIO device, iterate in .save_live_complete_precopy until > pending data is 0. > (FINISH_MIGRATE, _DEVICE, _STOPPED) I suggest we also register to VMStateDescription, whose .pre_save handler would get called after .save_live_complete_precopy in pre-copy only case, and will called before .save_live_iterate in post-copy enabled case. In the .pre_save handler, we can save all device state which must be copied after device stop in source vm and before device state in target vm. > | > (FINISH_MIGRATE, _COMPLETED, STOPPED) > Migraton thread schedule cleanup bottom half and exit > > Live migration resume path: > Incomming migration calls .load_setup for each device > (RESTORE_VM, _ACTIVE, STOPPED) > | > For each device, .load_state is called for that device section data > | > At the end, called .load_cleanup for each device and vCPUs are started. > | > (RUNNING, _NONE, _RUNNING) > > Note that: > - Migration post copy is not supported. > > v3 -> v4: > - Added one more bit for _RESUMING flag to be set explicitly. > - data_offset field is read-only for user space application. > - data_size is read for every iteration before reading data from migration, that > is removed assumption that data will be till end of migration region. > - If vendor driver supports mappable sparsed region, map those region during > setup state of save/load, similarly unmap those from cleanup routines. > - Handles race condition that causes data corruption in migration region during > save device state by adding mutex and serialiaing save_buffer and > get_dirty_pages routines. > - Skip called get_dirty_pages routine for mapped MMIO region of device. > - Added trace events. > - Splitted into multiple functional patches. > > v2 -> v3: > - Removed enum of VFIO device states. Defined VFIO device state with 2 bits. > - Re-structured vfio_device_migration_info to keep it minimal and defined action > on read and write access on its members. > > v1 -> v2: > - Defined MIGRATION region type and sub-type which should be used with region > type capability. > - Re-structured vfio_device_migration_info. This structure will be placed at 0th > offset of migration region. > - Replaced ioctl with read/write for trapped part of migration region. > - Added both type of access support, trapped or mmapped, for data section of the > region. > - Moved PCI device functions to pci file. > - Added iteration to get dirty page bitmap until bitmap for all requested pages > are copied. > > Thanks, > Kirti > > > Kirti Wankhede (13): > vfio: KABI for migration interface > vfio: Add function to unmap VFIO region > vfio: Add save and load functions for VFIO PCI devices > vfio: Add migration region initialization and finalize function > vfio: Add VM state change handler to know state of VM > vfio: Add migration state change notifier > vfio: Register SaveVMHandlers for VFIO device > vfio: Add save state functions to SaveVMHandlers > vfio: Add load state functions to SaveVMHandlers > vfio: Add function to get dirty page list > vfio: Add vfio_listerner_log_sync to mark dirty pages > vfio: Make vfio-pci device migration capable. > vfio: Add trace events in migration code path > > hw/vfio/Makefile.objs | 2 +- > hw/vfio/common.c | 55 +++ > hw/vfio/migration.c | 815 ++++++++++++++++++++++++++++++++++++++++++ > hw/vfio/pci.c | 126 ++++++- > hw/vfio/pci.h | 29 ++ > hw/vfio/trace-events | 19 + > include/hw/vfio/vfio-common.h | 22 ++ > linux-headers/linux/vfio.h | 71 ++++ > 8 files changed, 1132 insertions(+), 7 deletions(-) > create mode 100644 hw/vfio/migration.c > > -- > 2.7.0 >