public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	target-devel@vger.kernel.org,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] tcm_vhost: Add hotplug/hotunplug support
Date: Tue, 5 Mar 2013 16:34:17 +0200	[thread overview]
Message-ID: <20130305143416.GG2256@redhat.com> (raw)
In-Reply-To: <5135F150.1060206@redhat.com>

On Tue, Mar 05, 2013 at 02:21:20PM +0100, Paolo Bonzini wrote:
> Il 05/03/2013 13:11, Michael S. Tsirkin ha scritto:
> >> > +
> >> > +	struct vhost_work vs_event_work; /* evt injection work item */
> >> > +	struct llist_head vs_event_list; /* evt injection queue */
> >> > +
> >> > +	bool vs_events_dropped;
> > Documentation pls.
> > Also - how is this handled during migration?
> 
> Migration is not supported by vhost-scsi but yes, we would need to
> retrieve this bit.
> 
> Paolo

Well at the moment nothing is supported as there's no userspace
upstream :(

> > Don't we need a way for userspace to retrieve this bit?
> > 

  reply	other threads:[~2013-03-05 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05  9:17 [PATCH] tcm_vhost: Add hotplug/hotunplug support Asias He
2013-03-05  9:31 ` Wanlong Gao
2013-03-06  1:29   ` Asias He
2013-03-05 12:11 ` Michael S. Tsirkin
2013-03-05 13:21   ` Paolo Bonzini
2013-03-05 14:34     ` Michael S. Tsirkin [this message]
2013-03-05 22:51       ` Nicholas A. Bellinger
2013-03-06 14:28         ` Paolo Bonzini
2013-03-07  0:55           ` Asias He
2013-03-07 22:45             ` Nicholas A. Bellinger
2013-03-08  2:26               ` Asias He
2013-03-06  1:40       ` Asias He
2013-03-06  1:28   ` Asias He
2013-03-06 17:41     ` Paolo Bonzini
2013-03-07  0:36       ` Asias He

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=20130305143416.GG2256@redhat.com \
    --to=mst@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=target-devel@vger.kernel.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