From: Anthony Liguori <anthony@codemonkey.ws>
To: Ian Molton <ian.molton@collabora.co.uk>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option.
Date: Mon, 01 Feb 2010 16:54:50 -0600 [thread overview]
Message-ID: <4B675BBA.2080907@codemonkey.ws> (raw)
In-Reply-To: <4B675967.1060503@collabora.co.uk>
On 02/01/2010 04:44 PM, Ian Molton wrote:
> Anthony Liguori wrote:
>
>
>> I went back and looked at the last series and found my feedback. I had
>> suggested that instead of automatically reconnecting, a mechanism should
>> be added for a user to initiate a reconnect.
>>
> This sounds useful
>
>
>> Additionally, we should emit events upon disconnect through QMP (now
>> that we have that functionality).
>>
> This also.
>
>
>> The main reason I dislike automatic reconnecting is that there is no
>> correct way to handle the period of time while the VM is disconnected.
>>
> This is fine for egd protocol, the guest will just run low on entropy in
> the meantime. Nothing should break.
>
Right, but you're adding a generic piece of functionality. For
instance, what's the result of using reconnect with virtio-console? Is
this something that is going to work well?
>> Auto reconnecting is implementing a policy to handle the failure within
>> QEMU which is not universally the correct choice. This isn't so bad
>> except for the fact that you aren't providing the mechanisms for users
>> to implement other policies which means they're stuck with this
>> particular policy.
>>
> Perhaps this feature could be added if needed in future? It seems a bit
> ambitious to get all this 'right' with no use cases to test against.
>
I'm all for doing things incrementally but there has to be a big picture
that the incremental bit fits into otherwise you end up with a bunch of
random features that don't work together well.
Honestly, I'd strongly suggest splitting the reconnect logic out of the
series when resubmitting. I think it's just too hacky with too weak of
a justification. If you really want this functionality, we can discuss
the right approach for doing it but it's gotta be done in a way that's
not introducing a one-off case just for the random number generator.
Regards,
Anthony Liguori
> -Ian
>
next prev parent reply other threads:[~2010-02-01 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 13:34 [Qemu-devel] [PATCH] resend: socket reconnect and virtio-rng support Ian Molton
2010-02-01 13:34 ` [Qemu-devel] [PATCH 1/5] socket: Rationalise function declarations Ian Molton
2010-02-01 13:34 ` [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option Ian Molton
2010-02-01 13:34 ` [Qemu-devel] [PATCH 3/5] Add SIZE type to qdev properties Ian Molton
2010-02-01 13:34 ` [Qemu-devel] [PATCH 4/5] virtio: Add virtio-rng driver Ian Molton
2010-02-01 13:34 ` [Qemu-devel] [PATCH 5/5] Build fix (missing header) Ian Molton
2010-02-01 15:31 ` [Qemu-devel] [PATCH 4/5] virtio: Add virtio-rng driver Anthony Liguori
2010-02-01 16:03 ` Gerd Hoffmann
2010-02-01 16:50 ` Anthony Liguori
2010-02-01 22:41 ` Ian Molton
2010-02-01 22:48 ` Ian Molton
2010-02-09 10:50 ` Ian Molton
2010-02-01 15:25 ` [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option Anthony Liguori
2010-02-01 16:12 ` Luiz Capitulino
2010-02-01 16:49 ` Anthony Liguori
2010-02-01 22:44 ` Ian Molton
2010-02-01 22:54 ` Anthony Liguori [this message]
2010-02-02 10:23 ` Ian Molton
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=4B675BBA.2080907@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=ian.molton@collabora.co.uk \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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).