[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v8 05/13] x86: expose CBM length and COS number information
On Thu, 2015-05-28 at 14:26 +0100, Jan Beulich wrote: > >>> On 21.05.15 at 10:41, <chao.p.peng@xxxxxxxxxxxxxxx> wrote: > > --- a/xen/include/public/sysctl.h > > +++ b/xen/include/public/sysctl.h > > @@ -694,6 +694,20 @@ struct xen_sysctl_pcitopoinfo { > > typedef struct xen_sysctl_pcitopoinfo xen_sysctl_pcitopoinfo_t; > > DEFINE_XEN_GUEST_HANDLE(xen_sysctl_pcitopoinfo_t); > > > > +#define XEN_SYSCTL_PSR_CAT_get_l3_info 0 > > +struct xen_sysctl_psr_cat_op { > > + uint32_t cmd; /* IN: XEN_SYSCTL_PSR_CAT_* */ > > + uint32_t target; /* IN: socket to be operated on */ > > If this is always the socket number, why would the variable be > named anything other than "socket". If otoh subsequent patches > use it differently, I think the comment should be omitted now > rather than being dropped then (or it should be given its final > wording from the beginning). > ISTR asking about this interface before (it might have been at the toolstack level, though), and the answer was that it is not subsequent patches _in_this_series_ (of course), but maybe future ones that will modify the 'per-socket-ness' nature of this feature. So, yes, maybe the comment should say something along those lines (and be updated when things change). Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |