qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lan Tianyu <tianyu.lan@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: weiyang@linux.vnet.ibm.com, emil.s.tantilov@intel.com,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	jesse.brandeburg@intel.com, mark.d.rustad@intel.com,
	carolyn.wyborny@intel.com, eric.auger@linaro.org,
	donald.c.skidmore@intel.com, zajec5@gmail.com, agraf@suse.de,
	matthew.vick@intel.com, intel-wired-lan@lists.osuosl.org,
	jeffrey.t.kirsher@intel.com, gerlitz.or@gmail.com,
	mitch.a.williams@intel.com, nrupal.jani@intel.com,
	bhelgaas@google.com, a.motakis@virtualopensystems.com,
	b.reynal@virtualopensystems.com, linux-api@vger.kernel.org,
	shannon.nelson@intel.com, eddie.dong@intel.com,
	alex.williamson@redhat.com, linux-kernel@vger.kernel.org,
	john.ronciak@intel.com, netdev@vger.kernel.org,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH V2 3/3] Ixgbevf: Add migration support for ixgbevf driver
Date: Wed, 25 Nov 2015 13:39:32 +0800	[thread overview]
Message-ID: <56554994.1090305@intel.com> (raw)
In-Reply-To: <20151124230551-mutt-send-email-mst@redhat.com>

On 2015年11月25日 05:20, Michael S. Tsirkin wrote:
> I have to say, I was much more interested in the idea
> of tracking dirty memory. I have some thoughts about
> that one - did you give up on it then?

No, our finial target is to keep VF active before doing
migration and tracking dirty memory is essential. But this
seems not easy to do that in short term for upstream. As
starters, stop VF before migration.

After deep thinking, the way of stopping VF still needs tracking
DMA-accessed dirty memory to make sure the received data buffer
before stopping VF migrated. It's easier to do that via dummy writing
data buffer when receive packet.


-- 
Best regards
Tianyu Lan

  parent reply	other threads:[~2015-11-25  5:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 13:38 [Qemu-devel] [RFC PATCH V2 0/3] IXGBE/VFIO: Add live migration support for SRIOV NIC Lan Tianyu
2015-11-24 13:38 ` [Qemu-devel] [RFC PATCH V2 1/3] VFIO: Add new ioctl cmd VFIO_GET_PCI_CAP_INFO Lan Tianyu
2015-11-24 13:38 ` [Qemu-devel] [RFC PATCH V2 2/3] PCI: Add macros for faked PCI migration capability Lan Tianyu
2015-11-24 13:38 ` [Qemu-devel] [RFC PATCH V2 3/3] Ixgbevf: Add migration support for ixgbevf driver Lan Tianyu
2015-11-24 21:20   ` Michael S. Tsirkin
2015-11-25  5:39     ` Alexander Duyck
2015-11-25  5:39     ` Lan Tianyu [this message]
2015-11-25 12:28       ` Michael S. Tsirkin
2015-11-25 16:02         ` Lan, Tianyu
2015-11-25 16:22           ` Michael S. Tsirkin
2015-11-25 16:24           ` Alexander Duyck
2015-11-25 16:39             ` Michael S. Tsirkin
2015-11-25 17:24               ` Alexander Duyck
2015-11-24 14:20 ` [Qemu-devel] [RFC PATCH V2 0/3] IXGBE/VFIO: Add live migration support for SRIOV NIC Alexander Duyck
2015-11-25  3:18   ` Lan Tianyu
2015-11-25  5:30     ` Alexander Duyck
2015-11-25  8:21       ` Lan Tianyu
2015-11-25 15:32         ` Alexander Duyck
2015-11-26  3:15           ` Dong, Eddie
2015-11-26  3:56             ` Alexander Duyck
2015-11-30  6:53               ` Lan, Tianyu
2015-11-30 16:07                 ` Alexander Duyck
2015-12-01 15:04                   ` Lan, Tianyu
2015-12-01 15:28                     ` Michael S. Tsirkin
2015-12-01 17:04                       ` Alexander Duyck
2015-12-01 17:37                         ` Michael S. Tsirkin
2015-12-01 18:36                           ` Alexander Duyck
2015-12-02 11:44                             ` Michael S. Tsirkin
2015-12-04 16:32                               ` Lan, Tianyu
2015-12-04 17:07                                 ` Alexander Duyck
2015-12-07 15:40                                   ` Lan, Tianyu
2015-12-07 17:12                                     ` Alexander Duyck
2015-12-07 17:39                                       ` Michael S. Tsirkin
2015-12-07 18:42                                         ` Alexander Duyck
2015-12-09  9:28                                       ` Lan, Tianyu
2015-12-09 16:36                                         ` Alexander Duyck
2015-12-09 10:37                                 ` Michael S. Tsirkin
2015-12-09 11:19                                   ` Lan, Tianyu
2015-12-09 11:28                                     ` Michael S. Tsirkin
2015-12-09 11:41                                       ` Lan, Tianyu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56554994.1090305@intel.com \
    --to=tianyu.lan@intel.com \
    --cc=a.motakis@virtualopensystems.com \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=b.reynal@virtualopensystems.com \
    --cc=bhelgaas@google.com \
    --cc=carolyn.wyborny@intel.com \
    --cc=donald.c.skidmore@intel.com \
    --cc=eddie.dong@intel.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=eric.auger@linaro.org \
    --cc=gerlitz.or@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.d.rustad@intel.com \
    --cc=matthew.vick@intel.com \
    --cc=mitch.a.williams@intel.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nrupal.jani@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.nelson@intel.com \
    --cc=weiyang@linux.vnet.ibm.com \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).