2010/12/28 Michael S. Tsirkin <mst@xxxxxxxxxx>: > On Tue, Dec 28, 2010 at 08:34:12AM +0900, Yoshiaki Tamura wrote: >> 2010/12/28 Avi Kivity <avi@xxxxxxxxxx>: >> > 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 :) Thanks, Michael :) > 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? 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 :) One thumbs up here :) Yoshi > >> > >> > -- >> > error compiling committee.c: too many arguments to function >> > >> > >> > > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
