Il 05/10/2012 14:41, Luiz Capitulino ha scritto:
>>> > > That DPRINTF() usage is really bizarre, it seems its purpose is to
>>> > > report
>>> > > an error to the user, but that's a debugging call.
>>> > >
>>> > > I'd let it there and replace it later with proper tracing code, but
>>> > > that's
On Fri, 05 Oct 2012 08:25:46 +0200
Paolo Bonzini wrote:
> Il 04/10/2012 20:24, Luiz Capitulino ha scritto:
> > That DPRINTF() usage is really bizarre, it seems its purpose is to report
> > an error to the user, but that's a debugging call.
> >
> > I'd let it there and replace it later with prope
Il 04/10/2012 20:24, Luiz Capitulino ha scritto:
> That DPRINTF() usage is really bizarre, it seems its purpose is to report
> an error to the user, but that's a debugging call.
>
> I'd let it there and replace it later with proper tracing code, but that's
> quite minor for me. Please, at least me
On Wed, 3 Oct 2012 16:36:55 +0200
Paolo Bonzini wrote:
> Error propagation is already there for socket backends, but it
> is (and remains) incomplete because no Error is passed to the
> NonBlockingConnectHandler.
>
> With all protocols understanding Error, the code can be simplified
> by removi
Error propagation is already there for socket backends, but it
is (and remains) incomplete because no Error is passed to the
NonBlockingConnectHandler.
With all protocols understanding Error, the code can be simplified
by removing the return value.
Before:
(qemu) migrate fd:
migrate:
