public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Asias He <asias@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	target-devel@vger.kernel.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH V4 0/2] tcm_vhost hotplug
Date: Mon, 25 Mar 2013 16:20:09 +0800	[thread overview]
Message-ID: <20130325082009.GC20435@hj.localdomain> (raw)
In-Reply-To: <20130324152054.GC8657@redhat.com>

On Sun, Mar 24, 2013 at 05:20:54PM +0200, Michael S. Tsirkin wrote:
> On Fri, Mar 22, 2013 at 01:39:03PM +0800, Asias He wrote:
> > Asias He (2):
> >   tcm_vhost: Introduce tcm_vhost_check_feature()
> >   tcm_vhost: Add hotplug/hotunplug support
> 
> So this work should stay out of tree until we have
> 2 users for vhost-scsi, but I sent some comment to
> help you make progress.

Actually, I do not think the real reason you want to blcok/delay this
is that there is only one user. I believe the real reason is simply that
qemu is not using it. If there were already 2 users other than qemu
(qemu is still not using it), what would you say, you want 3 users of
this? Would you say the same 2 user thing, if a feature is only used by
qemu and other users are not using it?

Also, can you comment on Paolo's comment in the other thread.
"""
Il 19/03/2013 14:45, Michael S. Tsirkin ha scritto:
> On Tue, Mar 19, 2013 at 10:36:42AM +0100, Paolo Bonzini wrote:                                                                       
>> Il 18/03/2013 22:53, Michael S. Tsirkin ha scritto:                                                                                 
>>> Sorry, no, I'd prefer we get userspace support in qemu in first.                                                                   
>>> If there's only a single user for this driver (kvmtool),                                                                           
>>> then it was a mistake to merge it, the right thing would be to
>>> freeze it                                                           
>>> and look at whether we can drop it completely.                                                                                     
>>                                                                                                                                     
>> I'm still not sure why this matters for this patch, since it does not                                                               
>> change the userspace ABI.                                                                                                           
>                                                                                                                                      
> It enables a new feature bit.                                                                                                        

How does that matter if userspace is not supposed to do anything special
with that bit?

Paolo
"""

> >  drivers/vhost/tcm_vhost.c | 224 ++++++++++++++++++++++++++++++++++++++++++++--
> >  drivers/vhost/tcm_vhost.h |  10 +++
> >  2 files changed, 229 insertions(+), 5 deletions(-)
> > 
> > -- 
> > 1.8.1.4

-- 
Asias

  reply	other threads:[~2013-03-25  8:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  5:39 [PATCH V4 0/2] tcm_vhost hotplug Asias He
2013-03-22  5:39 ` [PATCH V4 1/2] tcm_vhost: Introduce tcm_vhost_check_feature() Asias He
2013-03-22  5:39 ` [PATCH V4 2/2] tcm_vhost: Add hotplug/hotunplug support Asias He
2013-03-24 15:20   ` Michael S. Tsirkin
     [not found]   ` <20130324152009.GB8657@redhat.com>
2013-03-25  7:48     ` Asias He
     [not found]     ` <20130325074806.GB20435@hj.localdomain>
2013-03-25 11:10       ` Michael S. Tsirkin
2013-03-26  2:56         ` Asias He
2013-03-26 20:46           ` Michael S. Tsirkin
2013-03-27  3:23             ` Asias He
2013-03-24 15:20 ` [PATCH V4 0/2] tcm_vhost hotplug Michael S. Tsirkin
2013-03-25  8:20   ` Asias He [this message]
2013-04-08 21:31 ` Nicholas A. Bellinger
2013-04-08 20:41   ` Michael S. Tsirkin
2013-04-09  0:57   ` Asias He
2013-04-08 21:36 ` Nicholas A. Bellinger

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=20130325082009.GC20435@hj.localdomain \
    --to=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --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