> -----Original Message-----
> From: George Dunlap [mailto:[email protected]]
> Sent: 10 July 2018 15:01
> To: Paul Durrant <[email protected]>; [email protected]
> Cc: Jan Beulich <[email protected]>; Andrew Cooper
> <[email protected]>; George Dunlap
> <[email protected]>; Ian Jackson <[email protected]>; Konrad
> Rzeszutek Wilk <[email protected]>; Stefano Stabellini
> <[email protected]>; Julien Grall <[email protected]>; Tim (Xen.org)
> <[email protected]>; Wei Liu <[email protected]>; Jun Nakajima
> <[email protected]>; Kevin Tian <[email protected]>
> Subject: Re: [PATCH v2 03/13] iommu: make use of type-safe BFN and MFN
> in exported functions
> 
> On 07/07/2018 12:05 PM, Paul Durrant wrote:
> > This patch modifies the declaration of the entry points to the IOMMU
> > sub-system to use bfn_t and mfn_t in place of unsigned long. A
> subsequent
> > patch will similarly modify the methods in the iommu_ops structure.
> >
> > Signed-off-by: Paul Durrant <[email protected]>
> > ---
> > Cc: Jan Beulich <[email protected]>
> > Cc: Andrew Cooper <[email protected]>
> > Cc: George Dunlap <[email protected]>
> > Cc: Ian Jackson <[email protected]>
> > Cc: Konrad Rzeszutek Wilk <[email protected]>
> > Cc: Stefano Stabellini <[email protected]>
> > Cc: Julien Grall <[email protected]>
> > Cc: Tim Deegan <[email protected]>
> > Cc: Wei Liu <[email protected]>
> > Cc: Jun Nakajima <[email protected]>
> > Cc: Kevin Tian <[email protected]>
> > Cc: George Dunlap <[email protected]>
> >
> > v2:
> >  - Addressed comments from Jan.
> >  - Use intermediate 'frame' variable to avoid directly encapsulating
> >    mfn or gfn values as bfns.
> 
> Explain this one to me?  At the moment I don't see any value from having
> the extra variable in the middle.

This was something that Jan wanted.

  Paul

> 
> Everything else looks good.
> 
>  -George
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to