On Thu, Aug 16, 2018 at 08:27:40PM +0200, Marc-André Lureau wrote:
> Hi
> On Thu, Aug 16, 2018 at 7:49 PM Marc-André Lureau
> wrote:
> >
> > Hi
> > On Tue, Mar 6, 2018 at 6:41 AM Peter Xu wrote:
> > >
> > > This patch allows the socket chardev async connection be setup with
> > > non-default gcon
Hi
On Thu, Aug 16, 2018 at 7:49 PM Marc-André Lureau
wrote:
>
> Hi
> On Tue, Mar 6, 2018 at 6:41 AM Peter Xu wrote:
> >
> > This patch allows the socket chardev async connection be setup with
> > non-default gcontext. We do it by postponing the setup to machine done,
> > since until then we can
Hi
On Tue, Mar 6, 2018 at 6:41 AM Peter Xu wrote:
>
> This patch allows the socket chardev async connection be setup with
> non-default gcontext. We do it by postponing the setup to machine done,
> since until then we can know which context we should run the async
> operation on.
>
> Reviewed-by:
On Tue, Mar 06, 2018 at 01:33:18PM +0800, Peter Xu wrote:
> This patch allows the socket chardev async connection be setup with
> non-default gcontext. We do it by postponing the setup to machine done,
> since until then we can know which context we should run the async
> operation on.
>
> Review
This patch allows the socket chardev async connection be setup with
non-default gcontext. We do it by postponing the setup to machine done,
since until then we can know which context we should run the async
operation on.
Reviewed-by: Paolo Bonzini
Signed-off-by: Peter Xu
---
chardev/char-socke
