Re: [PATCH v6 12/13] xen/pvcalls: implement release command

2017-10-26 Thread Stefano Stabellini
On Thu, 26 Oct 2017, Boris Ostrovsky wrote: > On 10/25/2017 07:00 PM, Stefano Stabellini wrote: > > On Wed, 25 Oct 2017, Boris Ostrovsky wrote: > >> On 10/24/2017 01:33 PM, Stefano Stabellini wrote: > >>> Send PVCALLS_RELEASE to the backend and wait for a reply. Take both > >>> in_mutex and out_mut

Re: [PATCH v6 12/13] xen/pvcalls: implement release command

2017-10-26 Thread Boris Ostrovsky
On 10/25/2017 07:00 PM, Stefano Stabellini wrote: > On Wed, 25 Oct 2017, Boris Ostrovsky wrote: >> On 10/24/2017 01:33 PM, Stefano Stabellini wrote: >>> Send PVCALLS_RELEASE to the backend and wait for a reply. Take both >>> in_mutex and out_mutex to avoid concurrent accesses. Then, free the >>> so

Re: [PATCH v6 12/13] xen/pvcalls: implement release command

2017-10-25 Thread Stefano Stabellini
On Wed, 25 Oct 2017, Boris Ostrovsky wrote: > On 10/24/2017 01:33 PM, Stefano Stabellini wrote: > > Send PVCALLS_RELEASE to the backend and wait for a reply. Take both > > in_mutex and out_mutex to avoid concurrent accesses. Then, free the > > socket. > > > > For passive sockets, check whether we h

Re: [PATCH v6 12/13] xen/pvcalls: implement release command

2017-10-25 Thread Boris Ostrovsky
On 10/24/2017 01:33 PM, Stefano Stabellini wrote: > Send PVCALLS_RELEASE to the backend and wait for a reply. Take both > in_mutex and out_mutex to avoid concurrent accesses. Then, free the > socket. > > For passive sockets, check whether we have already pre-allocated an > active socket for the pur

[PATCH v6 12/13] xen/pvcalls: implement release command

2017-10-24 Thread Stefano Stabellini
Send PVCALLS_RELEASE to the backend and wait for a reply. Take both in_mutex and out_mutex to avoid concurrent accesses. Then, free the socket. For passive sockets, check whether we have already pre-allocated an active socket for the purpose of being accepted. If so, free that as well. Signed-off