qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, dlaor@redhat.com,
	ananth@in.ibm.com, kvm@vger.kernel.org, mtosatti@redhat.com,
	ohmura.kei@lab.ntt.co.jp, qemu-devel@nongnu.org,
	Avi Kivity <avi@redhat.com>,
	vatsa@linux.vnet.ibm.com, psuriset@linux.vnet.ibm.com,
	stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] Re: [PATCH 18/19] Introduce -k option to enable FT migration mode (Kemari).
Date: Tue, 28 Dec 2010 01:45:00 +0200	[thread overview]
Message-ID: <20101227234500.GA22810@redhat.com> (raw)
In-Reply-To: <AANLkTikR3rfZ9eWASXr-cu97+Cw5r2epjKpu7jAKPKb4@mail.gmail.com>

On Tue, Dec 28, 2010 at 08:34:12AM +0900, Yoshiaki Tamura wrote:
> 2010/12/28 Avi Kivity <avi@redhat.com>:
> > On 12/27/2010 01:07 PM, Yoshiaki Tamura wrote:
> >>
> >> >>
> >> >>  >  Not sure whether we need to mention the codename here: is it likely
> >> >> to
> >> >>  >  help the users?
> >> >>
> >> >>  Ah:-)  Just didn't know what the official name should be, and
> >> >>  placed Kemari for convenience.  Any ideas or preference here?
> >> >>
> >> >>  Yoshi
> >> >
> >> >  Do we need a name? Fault tolerance mode insufficient?
> >>
> >> Not really.  Let's call it Fault Tolerance mode from now:-)
> >
> > Then -k becomes meaningless.  Rename to -fault-tolerant?
> 
> That's too long.  The option of migration is a single character
> conventionally.  In that sense, -f wasn't a good option because
> it usually reminds a file option, and -k was well fit not only
> because Kemari but also not well used and almost harmless.
> 
> So, my preference is to keep -k option, but that may be
> developer's (my) ego, and I'm happy to here what would be the
> best for qemu community.
> 
> Yoshi

Hey, that's imporant too :)

It's not hard to invent a reason for -k if we need one. E.g.
the protocol is specific to the Kemari project, right?
So the text could be 'Fault Tolerance mode (using Kemari protocol)'
to avoid potential confusion with other fault tolerance solutions
if we ever get them, and the option stays -k :)

> >
> > --
> > error compiling committee.c: too many arguments to function
> >
> >
> >

  reply	other threads:[~2010-12-27 23:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27  8:25 [Qemu-devel] [PATCH 00/19] Kemari for KVM v0.2.2 Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 01/19] Make QEMUFile buf expandable, and introduce qemu_realloc_buffer() and qemu_clear_buffer() Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 02/19] Introduce read() to FdMigrationState Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 03/19] Introduce skip_header parameter to qemu_loadvm_state() Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 04/19] qemu-char: export socket_set_nodelay() Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 05/19] vl.c: add deleted flag for deleting the handler Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 06/19] virtio: decrement last_avail_idx with inuse before saving Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 07/19] Introduce fault tolerant VM transaction QEMUFile and ft_mode Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 08/19] savevm: introduce util functions to control ft_trans_file from savevm layer Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 09/19] Introduce event-tap Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 10/19] Call init handler of event-tap at main() in vl.c Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 11/19] ioport: insert event_tap_ioport() to ioport_write() Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 12/19] Insert event_tap_mmio() to cpu_physical_memory_rw() in exec.c Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 13/19] net: insert event-tap to qemu_send_packet() and qemu_sendv_packet_async() Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 14/19] block: insert event-tap to bdrv_aio_writev() and bdrv_aio_flush() Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 15/19] savevm: introduce qemu_savevm_trans_{begin, commit} Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 16/19] migration: introduce migrate_ft_trans_{put, get}_ready(), and modify migrate_fd_put_ready() when ft_mode is on Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 17/19] migration-tcp: modify tcp_accept_incoming_migration() to handle ft_mode, and add a hack not to close fd when ft_mode is enabled Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 18/19] Introduce -k option to enable FT migration mode (Kemari) Yoshiaki Tamura
2010-12-27  8:56   ` [Qemu-devel] " Michael S. Tsirkin
2010-12-27  9:11     ` Yoshiaki Tamura
2010-12-27  9:32       ` Michael S. Tsirkin
2010-12-27 11:07         ` Yoshiaki Tamura
2010-12-27 17:11           ` Avi Kivity
2010-12-27 23:34             ` Yoshiaki Tamura
2010-12-27 23:45               ` Michael S. Tsirkin [this message]
2010-12-28  1:43                 ` Yoshiaki Tamura
2010-12-27  8:25 ` [Qemu-devel] [PATCH 19/19] migration: add a parser to accept FT migration incoming mode Yoshiaki Tamura
  -- strict thread matches above, loose matches on Subject: below --
2011-02-08 11:01 [Qemu-devel] [PATCH 00/19] Kemari for KVM v0.2.9 Yoshiaki Tamura
2011-02-08 11:01 ` [Qemu-devel] [PATCH 18/19] Introduce -k option to enable FT migration mode (Kemari) Yoshiaki Tamura
2011-02-08 12:13   ` [Qemu-devel] " Paolo Bonzini
2011-02-08 12:59     ` Yoshiaki Tamura

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=20101227234500.GA22810@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=avi@redhat.com \
    --cc=dlaor@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=ohmura.kei@lab.ntt.co.jp \
    --cc=psuriset@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=vatsa@linux.vnet.ibm.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).