netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Qin Chuanyu <qinchuanyu@huawei.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	jasowang@redhat.com, KVM list <kvm@vger.kernel.org>,
	netdev@vger.kernel.org, qianhuibin@huawei.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	wangfuhai@huawei.com, likunyun@huawei.com, liuyongan@huawei.com,
	liuyingdong@huawei.com
Subject: Re: Is fallback vhost_net to qemu for live migrate available?
Date: Mon, 2 Sep 2013 11:11:47 +0300	[thread overview]
Message-ID: <20130902081147.GA21387@redhat.com> (raw)
In-Reply-To: <20130902075722.GZ15729@zion.uk.xensource.com>

On Mon, Sep 02, 2013 at 08:57:22AM +0100, Wei Liu wrote:
> On Sat, Aug 31, 2013 at 12:45:11PM +0800, Qin Chuanyu wrote:
> > On 2013/8/30 0:08, Anthony Liguori wrote:
> > >Hi Qin,
> > 
> > >>By change the memory copy and notify mechanism ,currently virtio-net with
> > >>vhost_net could run on Xen with good performance。
> > >
> > >I think the key in doing this would be to implement a property
> > >ioeventfd and irqfd interface in the driver domain kernel.  Just
> > >hacking vhost_net with Xen specific knowledge would be pretty nasty
> > >IMHO.
> > >
> > Yes, I add a kernel module which persist virtio-net pio_addr and
> > msix address as what kvm module did. Guest wake up vhost thread by
> > adding a hook func in evtchn_interrupt.
> > 
> > >Did you modify the front end driver to do grant table mapping or is
> > >this all being done by mapping the domain's memory?
> > >
> > There is nothing changed in front end driver. Currently I use
> > alloc_vm_area to get address space, and map the domain's memory as
> > what what qemu did.
> > 
> 
> You mean you're using xc_map_foreign_range and friends in the backend to
> map guest memory? That's not very desirable as it violates Xen's
> security model. It would not be too hard to pass grant references
> instead of guest physical memory address IMHO.
> 
> Wei.

It's a start and it should make it fast and work with existing
infrastructure in the host, though.

-- 
MST

  reply	other threads:[~2013-09-02  8:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  3:32 Is fallback vhost_net to qemu for live migrate available? Qin Chuanyu
2013-08-27  4:19 ` Michael S. Tsirkin
2013-08-27  7:04   ` Qin Chuanyu
2013-08-27  7:16     ` Michael S. Tsirkin
2013-08-27  7:22       ` Qin Chuanyu
2013-08-27  9:41     ` Wei Liu
2013-08-29 16:08 ` Anthony Liguori
2013-08-31  4:45   ` Qin Chuanyu
2013-09-02  3:19     ` Jason Wang
2013-09-02  7:57     ` Wei Liu
2013-09-02  8:11       ` Michael S. Tsirkin [this message]
2013-09-03  1:28       ` Qin Chuanyu
2013-09-03  8:40         ` Wei Liu
2013-09-03  8:55           ` Michael S. Tsirkin
2013-09-03  9:15             ` Wei Liu
2013-09-05 13:33             ` [Xen-devel] " Stefano Stabellini
2013-10-14  8:19   ` Qin Chuanyu

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=20130902081147.GA21387@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=likunyun@huawei.com \
    --cc=liuyingdong@huawei.com \
    --cc=liuyongan@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=qianhuibin@huawei.com \
    --cc=qinchuanyu@huawei.com \
    --cc=wangfuhai@huawei.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).