[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH for-next v3 9/9] x86: introduce CONFIG_HYPERV and detection code
On Thu, Nov 21, 2019 at 05:59:16PM +0100, Jan Beulich wrote: > >> > >> Also how about having *_probe() return the address of *_ops, such > >> that the latter could all become static? > > > > Previously you made a suggestion to make probe return the name of the > > hypervisor. Here you ask for address of ops. I actually prefer the > > method suggested here, but this means I will need to keep > > hypervisor_name around. > > Is there actually any user of the name field other than the caller > of probe? If not, surely that caller could access the name field > without a hypervisor_name() wrapper. I don't envision more users at this stage. I'm fine with accessing that field directly. We can always introduce the function again if it becomes necessary. Wei. > > Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |