qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] configure: remove --enable-replication/--disable-replication
Date: Mon, 6 Feb 2017 11:57:00 +0000	[thread overview]
Message-ID: <20170206115659.GC2524@work-vm> (raw)
In-Reply-To: <55b46fa3-c861-9ba4-da65-25bc392d8900@redhat.com>

* Paolo Bonzini (pbonzini@redhat.com) wrote:
> 
> 
> On 03/02/2017 07:00, Stefan Hajnoczi wrote:
> > On Thu, Feb 02, 2017 at 07:05:30AM -0800, Paolo Bonzini wrote:
> >> The replication feature is a small amount of code, does not
> >> require any external library and unless used does not add
> >> anything to the guest's attack surface.  Since any extra
> >> configure option affects maintainability on the other hand
> >> and is subject to bit rot, I think there is no need to
> >> make it configurable.
> > 
> > I think the current state is good: replication is enabled by default but
> > can be compiled out if desired.
> > 
> > Downstreams may not be comfortable supporting this feature yet since
> > it's incomplete.  It's fair to offer an option to disable it, otherwise
> > downstreams will have to patch this themselves.
> 
> I understand---I just am not sure where to draw the line because there's
> plenty of other incomplete features, hence the RFC.  For example,
> record/replay cannot be enabled or disabled on the configure command
> line.  That was the case even in the beginning, where it didn't support
> either block or character device replay.

The line is certainly fuzzy, but I think it's worth making the following
type of things configurable:
   Features that have a large chunk of code
     - dont lets try and configure tiny things on and off
   That can be trivially configured
     - lets not put big chunks of code around making them configurable
and   that are incomplete
   or are unused by large chunks of the users

Dave

> --enable-coroutine-pool is a relic of when Windows builds needed it, but
> all other --enable-* options require an external library or at least a
> specific operating system.  See for example this patch:
> 
>     commit 52b53c04faab9f7a9879c8dc014930649a3e698d
>     Author: Fam Zheng <famz@redhat.com>
>     Date:   Wed Sep 10 14:17:51 2014 +0800
> 
>     block: Always compile virtio-blk dataplane
> 
>     Dataplane doesn't depend on linux-aio any more, so we don't need the
>     compiling condition now.
> 
>     Configure options are kept but just print a message.
> 
>     Signed-off-by: Fam Zheng <famz@redhat.com>
>     Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
>     Message-id: 1410329871-28885-4-git-send-email-famz@redhat.com
>     Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> 
> 
> I would actually prefer to remove many of the latter
> (--enable-vhost-net, --enable-vhost-scsi, --enable-vhost-socket) and
> just use default-configs.  We are already doing it for ivshmem for example:
> 
>     CONFIG_IVSHMEM=$(CONFIG_EVENTFD)
> 
> Paolo
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2017-02-06 11:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 15:05 [Qemu-devel] [RFC PATCH] configure: remove --enable-replication/--disable-replication Paolo Bonzini
2017-02-02 15:15 ` Dr. David Alan Gilbert
2017-02-03 15:00 ` Stefan Hajnoczi
2017-02-03 17:08   ` Paolo Bonzini
2017-02-06 11:57     ` Dr. David Alan Gilbert [this message]
2017-03-03 20:34       ` Bruce Rogers
2017-03-03 21:26         ` Paolo Bonzini
2017-03-06  9:08         ` Dr. David Alan Gilbert
2017-03-06 10:03           ` Zhang Chen
2017-03-06 12:54             ` Paolo Bonzini
2017-03-07  3:50               ` Zhang Chen

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=20170206115659.GC2524@work-vm \
    --to=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).