search for: op_shutdown

...> Thanks for this, I've been using it in my project and it mostly seems > fine. > > One wrinkle I came across, which I'm not sure if it is by design or a > problem is that I can see this sequence coming from the guest (with > other activity in between): > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > I orignally had my backend close things down at #2, however this meant > that when #3 arrived it was for a non-existent socket (or, worse, an > active...

...> Thanks for this, I've been using it in my project and it mostly seems > fine. > > One wrinkle I came across, which I'm not sure if it is by design or a > problem is that I can see this sequence coming from the guest (with > other activity in between): > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > I orignally had my backend close things down at #2, however this meant > that when #3 arrived it was for a non-existent socket (or, worse, an > active...

...tly seems > > > fine. > > > > > > One wrinkle I came across, which I'm not sure if it is by design or a > > > problem is that I can see this sequence coming from the guest (with > > > other activity in between): > > > > > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX How did you trigger this sequence? I'd like to reproduce it. > > > I orignally had my backend close things down at #2, however this...

...tly seems > > > fine. > > > > > > One wrinkle I came across, which I'm not sure if it is by design or a > > > problem is that I can see this sequence coming from the guest (with > > > other activity in between): > > > > > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX How did you trigger this sequence? I'd like to reproduce it. > > > I orignally had my backend close things down at #2, however this...

...n using it in my project and it mostly seems > > fine. > > > > One wrinkle I came across, which I'm not sure if it is by design or a > > problem is that I can see this sequence coming from the guest (with > > other activity in between): > > > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > > > I orignally had my backend close things down at #2, however this meant > > that when #3 arrived it was for a non-existent socket (...

...at.com> wrote: > > > > > One wrinkle I came across, which I'm not sure if it is by design or a > > > > problem is that I can see this sequence coming from the guest (with > > > > other activity in between): > > > > > > > > 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > > > 2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > > > 3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > How did you trigger this sequence? I'd like to reproduce it. > Nothing magic. I've written some logging into my ba...

...atest code should avoid duplicate work. Thanks for this, I've been using it in my project and it mostly seems fine. One wrinkle I came across, which I'm not sure if it is by design or a problem is that I can see this sequence coming from the guest (with other activity in between): ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX I orignally had my backend close things down at #2, however this meant that when #3 arrived it was for a non-existent socket (or, worse, an active one if the ports got reused)....

This series is based on Michael Tsirkin's vhost branch (v4.5-rc6). I'm about to process Claudio Imbrenda's locking fixes for virtio-vsock but first I want to share the latest version of the code. Several people are playing with vsock now so sharing the latest code should avoid duplicate work. v5: * Transport reset event for live migration support * Reorder virtqueues, drop unused

This series is based on Michael Tsirkin's vhost branch (v4.5-rc6). I'm about to process Claudio Imbrenda's locking fixes for virtio-vsock but first I want to share the latest version of the code. Several people are playing with vsock now so sharing the latest code should avoid duplicate work. v5: * Transport reset event for live migration support * Reorder virtqueues, drop unused

...ib/python/xen/xend/server/SrvBase.py", line 109, in _perform return self._perform_err(err, op, req) File "/usr/lib/python/xen/xend/server/SrvBase.py", line 107, in _perform val = op_method(op, req) File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 47, in op_shutdown val = fn(req.args, {''dom'': self.dom.id}) File "/usr/lib/python/xen/xend/Args.py", line 145, in __call__ return self.call_with_form_args(self.fn, fargs, xargs=xargs) File "/usr/lib/python/xen/xend/Args.py", line 121, in call_with_form_args return...

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *