Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
	Sridhar Samudrala <sridhar.samudrala@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	David Miller <davem@davemloft.net>,
	Netdev <netdev@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	virtio-dev@lists.oasis-open.org, "Brandeburg,
	Jesse" <jesse.brandeburg@intel.com>,
	"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
	Jakub Kicinski <kubakici@wp.pl>, Jason Wang <jasowang@redhat.com>,
	Siwei Liu <loseweigh@gmail.com>
Subject: [virtio-dev] Re: [RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
Date: Tue, 27 Feb 2018 23:23:35 +0200	[thread overview]
Message-ID: <20180227231731-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAKgT0Ucp8WhkORpVVy2VWwuvxZHZjXKn6YfHfVaLAVVybf3t5w@mail.gmail.com>

On Tue, Feb 27, 2018 at 01:16:21PM -0800, Alexander Duyck wrote:
> The other thing I am looking at is trying to find a good way to do
> dirty page tracking in the hypervisor using something like a
> para-virtual IOMMU. However I don't have any ETA on that as I am just
> starting out and have limited development time. If we get that in
> place we can leave the VF in the guest until the very last moments
> instead of having to remove it before we start the live migration.
> 
> - Alex

I actually think your old RFC would be a good starting point:
https://lkml.org/lkml/2016/1/5/104

What is missing is I think enabling/disabling dynamically.

Seems to be easier than tracking by the hypervisor.

-- 
MST

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2018-02-27 21:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 18:11 [virtio-dev] [RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device Sridhar Samudrala
2018-02-16 18:11 ` [virtio-dev] [RFC PATCH v3 1/3] virtio_net: Introduce VIRTIO_NET_F_BACKUP feature bit Sridhar Samudrala
2018-02-16 18:11 ` [virtio-dev] [RFC PATCH v3 2/3] virtio_net: Extend virtio to use VF datapath when available Sridhar Samudrala
2018-02-16 18:11 ` [virtio-dev] [RFC PATCH v3 3/3] virtio_net: Enable alternate datapath without creating an additional netdev Sridhar Samudrala
     [not found] ` <20180216183817.42b07af6@cakuba.netronome.com>
2018-02-17 17:12   ` [virtio-dev] Re: [RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device Alexander Duyck
     [not found]     ` <20180218221140.6c7fb32e@cakuba.netronome.com>
2018-02-20 16:26       ` Samudrala, Sridhar
2018-02-21 23:50     ` Siwei Liu
2018-02-22  0:17       ` Alexander Duyck
2018-02-22  1:59         ` Siwei Liu
2018-02-22  2:35           ` Samudrala, Sridhar
2018-02-22  3:28             ` Samudrala, Sridhar
2018-02-23 22:22             ` Siwei Liu
     [not found]               ` <20180223223802.GA2010@nanopsycho>
2018-02-24  0:17                 ` Siwei Liu
     [not found]         ` <20180223160305.71fb2db2@xeon-e3>
2018-02-25 22:17           ` Alexander Duyck
     [not found] ` <20180220104224.GA2031@nanopsycho>
2018-02-20 16:04   ` Alexander Duyck
     [not found]     ` <20180220162933.GD2031@nanopsycho>
2018-02-20 17:14       ` Samudrala, Sridhar
     [not found]         ` <20180220201410.GF2031@nanopsycho>
2018-02-20 21:02           ` Alexander Duyck
     [not found]           ` <20180220143356.3467084d@cakuba.netronome.com>
     [not found]             ` <20180221095159.GA1996@nanopsycho>
2018-02-21 15:56               ` Alexander Duyck
     [not found]                 ` <20180221161105.GC1996@nanopsycho>
2018-02-21 16:49                   ` Alexander Duyck
     [not found]                     ` <20180221165848.GD1996@nanopsycho>
2018-02-21 17:56                       ` Alexander Duyck
     [not found]                         ` <20180221193832.GE1996@nanopsycho>
2018-02-21 20:57                           ` Alexander Duyck
     [not found]                             ` <20180221180213.30885283@cakuba.netronome.com>
2018-02-22  2:15                               ` Samudrala, Sridhar
     [not found]                             ` <20180222081115.GC1994@nanopsycho>
     [not found]                               ` <CAJ3xEMiWUY1-zoFTJ9C9QeAGt24bVg-kKO8RkvRa8Agaf2R+0A@mail.gmail.com>
     [not found]                                 ` <20180222130717.GE1994@nanopsycho>
2018-02-22 15:30                                   ` Alexander Duyck
2018-02-22 21:30                               ` Alexander Duyck
     [not found]                                 ` <20180223155904.27b11865@xeon-e3>
2018-02-25 22:21                                   ` Alexander Duyck
     [not found]                                   ` <20180226071924.GA2063@nanopsycho>
     [not found]                                     ` <20180226170218.6b1dcf22@xeon-e3>
2018-02-27  1:18                                       ` Michael S. Tsirkin
2018-02-20 17:23       ` Alexander Duyck
     [not found]     ` <20180227084959.GB2005@nanopsycho>
2018-02-27 21:16       ` Alexander Duyck
2018-02-27 21:23         ` Michael S. Tsirkin [this message]
     [not found]         ` <20180227134149.2bff667e@cakuba.netronome.com>
     [not found]           ` <20180228070839.GA19654@nanopsycho>
2018-02-28 14:32             ` Michael S. Tsirkin
     [not found]               ` <20180228151131.GF19654@nanopsycho>
2018-02-28 15:45                 ` Michael S. Tsirkin
     [not found]                   ` <20180228192501.GB2389@nanopsycho>
2018-02-28 20:48                     ` Michael S. Tsirkin
2018-02-27 21:30       ` Michael S. Tsirkin

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=20180227231731-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kubakici@wp.pl \
    --cc=loseweigh@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sridhar.samudrala@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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