From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH 3/4 RFC] x86/p2m: use large pages for MMIO mappings Date: Tue, 29 Sep 2015 14:06:20 +0100 Message-ID: <560A8CCC.5030805@citrix.com> References: <55F70C9A02000078000A2A58@prv-mh.provo.novell.com> <55F7E13902000078000A2B7E@prv-mh.provo.novell.com> <55F7E13902000078000A2B7E@prv-mh.provo.novell.com> <55F7E63702000078000A2BD6@prv-mh.provo.novell.com> <560A7700.6010309@citrix.com> <560A95AA02000078000A69A5@prv-mh.provo.novell.com> <560A8131.7040901@citrix.com> <560AA45302000078000A6A47@prv-mh.provo.novell.com> <560A8993.2050601@citrix.com> <560AA78702000078000A6A90@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Zgueg-00074x-3i for xen-devel@lists.xenproject.org; Tue, 29 Sep 2015 13:09:14 +0000 In-Reply-To: <560AA78702000078000A6A90@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Wei Liu , Stefano Stabellini , George Dunlap , Andrew Cooper , Ian Jackson , Ian Campbell , xen-devel , Tiejun Chen , MalcolmCrossley , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 29/09/15 14:00, Jan Beulich wrote: >>>> On 29.09.15 at 14:52, wrote: >> On 29/09/15 13:46, Jan Beulich wrote: >>> Again, make map_mmio_regions() a wrapper around an ARM-specific >>> function with the extra argument. No need to alter common or x86 >>> code. >> >> TBH, extending the mapp_mmio_region is the best solution. >> >> The name map_mmio_region is very generic and there is no reason we can't >> use it in the hypervisor. Adding yet another wrapper will confuse people >> and it will be hard for both the reviewer and the developer to know >> which one to use. > > I disagree - the function was originally meant to exclusively support > the respective domctl. The fact that ARM gained (many) more uses > should not impact common code or x86. The expectation you described is neither documented nor explicit from the name... As the interface is not set in stone, we could decide to extend the usage of the function to make a coherent interface and not adding new wrapper because we don't want to touch x86... Anyway, I'm not a maintainer so I will let Ian and Stefano decide what's best. Regards, -- Julien Grall