From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v4] x86/p2m: use large pages for MMIO mappings Date: Mon, 25 Jan 2016 14:21:44 +0000 Message-ID: <1453731704.4320.173.camel@citrix.com> References: <56A25C0602000078000CA367@prv-mh.provo.novell.com> <1453724207.4320.137.camel@citrix.com> <56A6371802000078000CAA6B@prv-mh.provo.novell.com> <1453730752.4320.164.camel@citrix.com> <56A63C4002000078000CAAA7@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.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aNi1g-0001KN-30 for xen-devel@lists.xenproject.org; Mon, 25 Jan 2016 14:21:52 +0000 In-Reply-To: <56A63C4002000078000CAAA7@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: Kevin Tian , Wei Liu , Stefano Stabellini , George Dunlap , Andrew Cooper , Ian Jackson , Tim Deegan , Jun Nakajima , xen-devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Mon, 2016-01-25 at 07:16 -0700, Jan Beulich wrote: > > > > On 25.01.16 at 15:05, wrote: > > On Mon, 2016-01-25 at 06:54 -0700, Jan Beulich wrote: > > > > > > On 25.01.16 at 13:16, wrote: > > > > On Fri, 2016-01-22 at 08:42 -0700, Jan Beulich wrote: > > > > > +#define MAP_MMIO_MAX_ITER 64 /* pretty arbitrary */ > > > > > + > > > > > > > > I suppose no existing in-tree code exceeds that (or there'd be more > > > > patch > > > > here). > > > > > > There simply is no in-tree user other than the domctl on x86. > > > > Right, I meant callers of the domctl (via libxc) > > Then I don't understand the question. The domctl clearly can be > invoked with higher MFN counts; the #define only establishes > the cut off point for the code to return "partial success", directing > the caller to re-invoke the operation after updating inputs. I.e. > nothing else than an implementation detail which could be changed > without affecting any well behaved caller. Sorry, I'd confused myself into thinking the eventual caller would need to handle the E2BIG, whereas you (of course) deal with it in the libxc wrapper. Ian.