virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Asias He <asias@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 V2 0/6] tcm_vhost hotplug/hotunplug support and locking/flushing fix
Date: Tue, 12 Mar 2013 11:55:14 +0200	[thread overview]
Message-ID: <20130312095514.GC22633@redhat.com> (raw)
In-Reply-To: <20130312023109.GF1480@hj.localdomain>

On Tue, Mar 12, 2013 at 10:31:09AM +0800, Asias He wrote:
> On Mon, Mar 11, 2013 at 02:03:27PM +0200, Michael S. Tsirkin wrote:
> > On Fri, Mar 08, 2013 at 10:21:41AM +0800, Asias He wrote:
> > > Changes in v2:
> > > - Remove code duplication in tcm_vhost_{hotplug,hotunplug}
> > > - Fix racing of vs_events_nr
> > > - Add flush fix patch to this series
> > > Asias He (6):
> > >   tcm_vhost: Add missed lock in vhost_scsi_clear_endpoint()
> > >   tcm_vhost: Introduce tcm_vhost_check_feature()
> > >   tcm_vhost: Introduce tcm_vhost_check_endpoint()
> > >   tcm_vhost: Fix vs->vs_endpoint checking in vhost_scsi_handle_vq()
> > >   tcm_vhost: Add hotplug/hotunplug support
> > >   tcm_vhost: Flush vhost_work in vhost_scsi_flush()
> > > 
> > 
> > Are all these patches bugfixes?
> 
> Nope.
> 
> > Please don't add any more features in kernel until qemu starts using
> > this driver. 
> 
> Why? Why should qemu prevent from improving the driver and the benefit
> to the other user of the driver? Kvm tool is already using it since last
> Aug. This adds the missing disk hotplug support to kvm tool.

Basically we shouldn't add stuff to kernel for a single user.
Before we commit to support features forever, let's take the time
to see that the interfaces satisfy the requirements of multiple users.
It doesn't have to be qemu but we need to see several users.

> Plus, this
> is not a pure "feature", it is designed in virtio-scsi spec. 

The spec doesn't say it's a mandatory feature or did I miss something?

> > We put it in kernel after at the KVM forum it looked like
> > everyone agrees it's useful and qemu and kvmtool will use it, but it has
> > been in kernel since July and qemu patches are still outstanding.
> 
> I am working on the qemu bits where Paolo and Nicholas left.

Great.

> > If only part of the patches are bugfixes could you please separate them
> > out and submit for 3.9?
> 
> I will separate patch 2 and 5 for hotplug support and others for
> bugfixes.

Thanks.

> > Thanks,
> > 
> > >  drivers/vhost/tcm_vhost.c | 243 ++++++++++++++++++++++++++++++++++++++++++++--
> > >  drivers/vhost/tcm_vhost.h |  10 ++
> > >  2 files changed, 247 insertions(+), 6 deletions(-)
> > > 
> > > -- 
> > > 1.8.1.4
> 
> -- 
> Asias

  reply	other threads:[~2013-03-12  9:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  2:21 [PATCH V2 0/6] tcm_vhost hotplug/hotunplug support and locking/flushing fix Asias He
2013-03-08  2:21 ` [PATCH V2 1/6] tcm_vhost: Add missed lock in vhost_scsi_clear_endpoint() Asias He
2013-03-08  2:21 ` [PATCH V2 2/6] tcm_vhost: Introduce tcm_vhost_check_feature() Asias He
2013-03-08  2:21 ` [PATCH V2 3/6] tcm_vhost: Introduce tcm_vhost_check_endpoint() Asias He
2013-03-08  2:21 ` [PATCH V2 4/6] tcm_vhost: Fix vs->vs_endpoint checking in vhost_scsi_handle_vq() Asias He
2013-03-08  2:21 ` [PATCH V2 5/6] tcm_vhost: Add hotplug/hotunplug support Asias He
2013-03-08  2:21 ` [PATCH V2 6/6] tcm_vhost: Flush vhost_work in vhost_scsi_flush() Asias He
2013-03-08  8:24 ` [PATCH V2 0/6] tcm_vhost hotplug/hotunplug support and locking/flushing fix Stefan Hajnoczi
2013-03-11 12:03 ` Michael S. Tsirkin
2013-03-12  2:31   ` Asias He
2013-03-12  9:55     ` Michael S. Tsirkin [this message]
2013-03-13  3:29       ` Asias He
2013-03-13  8:11       ` Paolo Bonzini

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=20130312095514.GC22633@redhat.com \
    --to=mst@redhat.com \
    --cc=asias@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;
as well as URLs for NNTP newsgroup(s).