From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH v5] x86/p2m: use large pages for MMIO mappings Date: Wed, 27 Jan 2016 10:28:36 +0000 Message-ID: <56A89BD4.6030008@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> <1453731704.4320.173.camel@citrix.com> <56A658FE02000078000CAC3D@prv-mh.provo.novell.com> <56A8A88F02000078000CB780@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 1aONLK-0003Lo-Mr for xen-devel@lists.xenproject.org; Wed, 27 Jan 2016 10:28:54 +0000 In-Reply-To: <56A8A88F02000078000CB780@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 , Kevin Tian Cc: Wei Liu , Ian Campbell , Stefano Stabellini , George Dunlap , Tim Deegan , Ian Jackson , Jun Nakajima , xen-devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 27/01/16 10:22, Jan Beulich wrote: >>>> On 26.01.16 at 23:35, wrote: >>> From: Jan Beulich [mailto:JBeulich@suse.com] >>> Sent: Tuesday, January 26, 2016 12:19 AM >>> >>> When mapping large BARs (e.g. the frame buffer of a graphics card) the >>> overhead of establishing such mappings using only 4k pages has, >>> particularly after the XSA-125 fix, become unacceptable. Alter the >>> XEN_DOMCTL_memory_mapping semantics once again, so that there's no >>> longer a fixed amount of guest frames that represents the upper limit >>> of what a single invocation can map. Instead bound execution time by >>> limiting the number of iterations (regardless of page size). >>> >>> Signed-off-by: Jan Beulich >> Acked-by: Kevin Tian for VMX part. >> >> Curious. When you say "become unacceptable", how bad is it? mostly >> impact the boot time? > Yes, guest boot time. I don't have a reference to the original report > at hand, but that was what someone (Konrad?) had reported. I've > never seen the issue myself, largely because I've never made any > attempt at GPU pass-through. >>From XenServer testing, with a 1GB GPU BAR, XSA-125 caused and additional 70s of guest boot time. Naturally. we had to work around this. Partly upping the repeat limit, and deferring VT-d flushes. ~Andrew