qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 3/5] xen: create wrappers for all other uses of


From: Anthony PERARD
Subject: Re: [Qemu-devel] [PATCH 3/5] xen: create wrappers for all other uses of xc_hvm_XXX() functions
Date: Thu, 2 Mar 2017 10:44:59 +0000
User-agent: Mutt/1.8.0 (2017-02-23)

On Wed, Mar 01, 2017 at 04:16:32PM +0000, Paul Durrant wrote:
> > -----Original Message-----
> > From: Anthony PERARD [mailto:address@hidden
> > Sent: 01 March 2017 16:14
> > To: Paul Durrant <address@hidden>
> > Cc: address@hidden; address@hidden; Stefano
> > Stabellini <address@hidden>; Paolo Bonzini <address@hidden>;
> > Richard Henderson <address@hidden>; Eduardo Habkost
> > <address@hidden>; Michael S. Tsirkin <address@hidden>
> > Subject: Re: [PATCH 3/5] xen: create wrappers for all other uses of
> > xc_hvm_XXX() functions
> > 
> > On Thu, Feb 23, 2017 at 02:53:53PM +0000, Paul Durrant wrote:
> > > This patch creates inline wrapper functions in xen_common.h for all open
> > > coded calls to xc_hvm_XXX() functions outside of xen_common.h so that
> > use
> > > of xen_xc can be made implicit. This again is in preparation for the move
> > > to using libxendevicemodel.
> > >
> > > Signed-off-by: Paul Durrant <address@hidden>
> > > ---
> > > diff --git a/include/hw/xen/xen_common.h
> > b/include/hw/xen/xen_common.h
> > > index 1e08b98..31cf25f 100644
> > > --- a/include/hw/xen/xen_common.h
> > > +++ b/include/hw/xen/xen_common.h
> > > @@ -26,6 +26,50 @@ extern xc_interface *xen_xc;
> > >   * We don't support Xen prior to 4.2.0.
> > >   */
> > >
> > > +static inline int xen_set_mem_type(domid_t domid, hvmmem_type_t
> > type,
> > > +                                   uint64_t first_pfn, uint32_t nr)
> > > +{
> > 
> > I don't know if it matters from where the functions are called, but
> > here, xc_hvm_set_mem_type takes a "uint64_t nr" (and not uint32_t).
> 
> Yes, the old APIs were wrong and discarded the upper 32 bits, so limiting 
> here is correct. Moving to the new API fixes the issue.

OK, thanks.

In that case:
Reviewed-by: Anthony PERARD <address@hidden>

-- 
Anthony PERARD



reply via email to

[Prev in Thread] Current Thread [Next in Thread]