On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: > On Wed, Jun 24, 2015 at 2:06 PM, Ed White <edmund.h.wh...@intel.com > <mailto:edmund.h.wh...@intel.com>> wrote: > On 06/24/2015 09:15 AM, Lengyel, Tamas wrote: > >> +bool_t p2m_set_altp2m_mem_access(struct domain *d, uint16_t idx, > >> + unsigned long pfn, xenmem_access_t > >> access) > >> +{ > >> > > > > This function IMHO should be merged with p2m_set_mem_access and should > be > > triggerable with the same memop (XENMEM_access_op) hypercall instead of > > introducing a new hvmop one. > > I think we should vote on this. My view is that it makes > XENMEM_access_op > too complicated to use. > > The two functions are not very long and share enough code that it would > justify merging. The only big change added is the copy from host->alt > when the entry doesn't exists in alt, and that itself is pretty self > contained. Let's see if we can get a third opinion on it..
At first sight (I admit I'm rather late in the game and haven't had a chance to follow the series closely from the beginning), the two functions do seem to be mergeable (or at least the common code factored out in static helper functions). Also, if Ed's concern is that the libxc API would look unnatural if xc_set_mem_access() is used for both purposes, as far as I can tell the only difference could be a non-zero last altp2m parameter, so I agree with you that the less functions doing almost the same thing the better (I have been guilty of this in the past too, for example with my xc_enable_introspection() function ;) ). So I'd say, yes, if possible merge them. Regards, Razvan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
