Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2019-01-07 Thread Christopher Clark
On Fri, Jan 4, 2019 at 5:37 AM Jan Beulich wrote: > > >>> On 04.01.19 at 09:13, wrote: > > ok, I'm at the point where I'm close to having a version three of the > > series to post that addresses all the feedback so far, plus some > > additional improvements, with the following two items remaining

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2019-01-04 Thread Jan Beulich
>>> On 04.01.19 at 09:13, wrote: > ok, I'm at the point where I'm close to having a version three of the > series to post that addresses all the feedback so far, plus some > additional improvements, with the following two items remaining to > discuss: > > 1) the domain_cookie, with Jan's question

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2019-01-04 Thread Roger Pau Monné
On Fri, Jan 04, 2019 at 12:13:09AM -0800, Christopher Clark wrote: > 2) the p2m type of the guest-supplied memory for the ring. > > Roger raised a query about not pinning the p2m type of memory > used for the ring, and my response on 21st December is here: > > https://lists.xenproject.org/archive

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2019-01-04 Thread Christopher Clark
On Thu, Dec 20, 2018 at 12:33 AM Jan Beulich wrote: > > >>> On 20.12.18 at 06:58, wrote: > > On Wed, Dec 12, 2018 at 3:53 AM Jan Beulich wrote: > >> >>> On 01.12.18 at 02:32, wrote: > >> > +static struct argo_ring_info * > >> > +argo_ring_find_info_by_match(const struct domain *d, uint32_t port

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2018-12-20 Thread Jan Beulich
>>> On 20.12.18 at 06:58, wrote: > On Wed, Dec 12, 2018 at 3:53 AM Jan Beulich wrote: >> >>> On 01.12.18 at 02:32, wrote: >> > +static struct argo_ring_info * >> > +argo_ring_find_info_by_match(const struct domain *d, uint32_t port, >> > + domid_t partner_id, uint64_t

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2018-12-19 Thread Christopher Clark
On Wed, Dec 12, 2018 at 3:53 AM Jan Beulich wrote: > > >>> On 01.12.18 at 02:32, wrote: > > +static void > > +argo_signal_domain(struct domain *d) > > +{ > > +argo_dprintk("signalling domid:%d\n", d->domain_id); > > + > > +if ( !d->argo ) /* This can happen if the domain is being destroye

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2018-12-12 Thread Jan Beulich
>>> On 01.12.18 at 02:32, wrote: > +static void > +argo_signal_domain(struct domain *d) > +{ > +argo_dprintk("signalling domid:%d\n", d->domain_id); > + > +if ( !d->argo ) /* This can happen if the domain is being destroyed */ > +return; If such a precaution is necessary, how is i

Re: [Xen-devel] [PATCH 15/25] argo: implement the sendv op

2018-12-04 Thread Paul Durrant
> -Original Message- > From: Christopher Clark [mailto:christopher.w.cl...@gmail.com] > Sent: 01 December 2018 01:33 > To: xen-devel@lists.xenproject.org > Cc: Andrew Cooper ; George Dunlap > ; Ian Jackson ; Jan > Beulich ; Julien Grall ; Konrad > Rzeszutek Wilk ; Stefano Stabellini > ; Tim

[Xen-devel] [PATCH 15/25] argo: implement the sendv op

2018-11-30 Thread Christopher Clark
sendv operation is invoked to perform a synchronous send of buffers contained in iovs to a remote domain's registered ring. It takes: * A destination address (domid, port) for the ring to send to. It performs a most-specific match lookup, to allow for wildcard. * A source address, used to inf