Re: [Xen-devel] [PATCH v2 07/10] vm_event: Add vm_event_ng interface

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Petre Ovidiu PIRCALABU <ppircalabu@xxxxxxxxxxxxxxx>
> Sent: 19 July 2019 12:24
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>; 'Jan Beulich' <JBeulich@xxxxxxxx>
> Cc: JulienGrall <julien.grall@xxxxxxx>; Alexandru Stefan ISAILA 
> <aisaila@xxxxxxxxxxxxxxx>; Razvan
> Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>; Andrew Cooper 
> <Andrew.Cooper3@xxxxxxxxxx>; George Dunlap
> <George.Dunlap@xxxxxxxxxx>; Ian Jackson <Ian.Jackson@xxxxxxxxxx>; Roger Pau 
> Monne
> <roger.pau@xxxxxxxxxx>; Stefano Stabellini <sstabellini@xxxxxxxxxx>; 
> xen-devel@xxxxxxxxxxxxxxxxxxxx;
> KonradRzeszutek Wilk <konrad.wilk@xxxxxxxxxx>; Tamas K Lengyel 
> <tamas@xxxxxxxxxxxxx>; Tim (Xen.org)
> <tim@xxxxxxx>; Wei Liu <wl@xxxxxxx>
> Subject: Re: [PATCH v2 07/10] vm_event: Add vm_event_ng interface
> 
> On Fri, 2019-07-19 at 08:26 +0000, Paul Durrant wrote:
> > > -----Original Message-----
> > > From: Jan Beulich <JBeulich@xxxxxxxx>
> > > Sent: 19 July 2019 09:22
> > > To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> > > Cc: 'Petre Ovidiu PIRCALABU' <ppircalabu@xxxxxxxxxxxxxxx>;
> > > JulienGrall <julien.grall@xxxxxxx>;
> > > Alexandru Stefan ISAILA <aisaila@xxxxxxxxxxxxxxx>; Razvan Cojocaru
> > > <rcojocaru@xxxxxxxxxxxxxxx>; Andrew
> > > Cooper <Andrew.Cooper3@xxxxxxxxxx>; George Dunlap <
> > > George.Dunlap@xxxxxxxxxx>; Ian Jackson
> > > <Ian.Jackson@xxxxxxxxxx>; Roger Pau Monne <roger.pau@xxxxxxxxxx>;
> > > Stefano Stabellini
> > > <sstabellini@xxxxxxxxxx>; xen-devel@xxxxxxxxxxxxxxxxxxxx;
> > > KonradRzeszutek Wilk
> > > <konrad.wilk@xxxxxxxxxx>; Tamas K Lengyel <tamas@xxxxxxxxxxxxx>;
> > > Tim (Xen.org) <tim@xxxxxxx>; Wei Liu
> > > <wl@xxxxxxx>
> > > Subject: Re: [PATCH v2 07/10] vm_event: Add vm_event_ng interface
> > >
> > > On 19.07.2019 09:56, Paul Durrant wrote:
> > > > > From: Petre Ovidiu PIRCALABU <ppircalabu@xxxxxxxxxxxxxxx>
> > > > > Sent: 18 July 2019 14:59
> > > > >
> > > > > So, at this point the most promising solution is allocating the
> > > > > memory
> > > > > in XEN, sharing it with ID using share_xen_page_with_guest, and
> > > > > mapping
> > > > > it with xenforeignmemory_map_resource (with the flag
> > > > > XENMEM_rsrc_acq_caller_owned set)
> > > >
> > > > If that page is shared with the ID then
> > > > XENMEM_rsrc_acq_caller_owned
> > > > should *not* be set. Also, that flag is an 'out' flag... the
> > > > caller
> > > > doesn't decide who owns the resource.
> > >
> > > I had implied that it's really MD that's meant here, but maybe I
> > > was
> > > wrong doing so.
> > >
> > > > TBH I regret ever introducing the flag; it caused a lot of
> > > > problems,
> > > > which is why it is no longer used.
> > >
> > > It's a tools only interface - why don't we drop the flag if you now
> > > think it was a bad idea to introduce it?
> >
> > I was indeed thinking I should find enough tuits to do that in the
> > near future.
> >
> >   Paul
> >
> > >
> > > Jan
> Sorry, my mistake. I meant to say it's shared with MD.
> 
> Many thanks for your support,

Ok, in that case please share with the ID instead. I found some tuits this 
morning and am about to a submit a patch.

  Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel