From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tian, Kevin" Subject: Re: [PATCH v3 3/3] tools: introduce parameter max_wp_ram_ranges. Date: Fri, 5 Feb 2016 03:47:24 +0000 Message-ID: References: <1454064314-7799-1-git-send-email-yu.c.zhang@linux.intel.com> <56B0CE8102000078000CD8D4@prv-mh.provo.novell.com> <56B0C485.8070206@linux.intel.com> <56B0D7A202000078000CD989@prv-mh.provo.novell.com> <56B1A7C9.2010708@linux.intel.com> <56B1C93002000078000CDD4B@prv-mh.provo.novell.com> <6b6d0558d3c24f9483ad41d88ced9837@AMSPEX02CL03.citrite.net> <56B2023E02000078000CE01A@prv-mh.provo.novell.com> <7316ea5cb41543d69d7727721368e3c8@AMSPEX02CL03.citrite.net> <56B207EA02000078000CE0A8@prv-mh.provo.novell.com> <9467b97e15bc4cb1b8d6c948ad4fc926@AMSPEX02CL03.citrite.net> <56B20BFA02000078000CE0E7@prv-mh.provo.novell.com> <621ce95774ac4742b96ed9d504c08670@AMSPEX02CL03.citrite.net> <22194.4639.132613.604758@mariner.uk.xensource.com> <56B310D7.7010506@linux.intel.com> <44e528cd11744242961d46c6f87d2bb9@AMSPEX02CL03.citrite.net> <56B31C1C.3000907@linux.intel.com> <56B3373B02000078000CE86C@prv-mh.provo.novell.com> <22195.21299.624759.118961@mariner.uk.xensource.com> <347fa8fe5fdc4ba8adb6bc4502926838@AMSPEX02CL03.citrite.net> <56B36A6302000078000CE9E8@prv-mh.provo.novell.com> <3eaca9ee3fb34adbac7cce14301953c7@AMSPEX02CL03.citrite.net> <22195.26854.883844.693483@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant , Ian Jackson Cc: Wei Liu , Ian Campbell , Andrew Cooper , George Dunlap , "xen-devel@lists.xen.org" , Stefano Stabellini , "Lv, Zhiyuan" , Jan Beulich , Zhang Yu , "Keir (Xen.org)" List-Id: xen-devel@lists.xenproject.org > From: Paul Durrant [mailto:Paul.Durrant@citrix.com] > Sent: Thursday, February 04, 2016 11:51 PM > > > -----Original Message----- > > From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com] > > Sent: 04 February 2016 15:06 > > To: Paul Durrant > > Cc: Jan Beulich; Andrew Cooper; George Dunlap; Ian Campbell; Stefano > > Stabellini; Wei Liu; Kevin Tian; zhiyuan.lv@intel.com; Zhang Yu; xen- > > devel@lists.xen.org; Keir (Xen.org) > > Subject: RE: [Xen-devel] [PATCH v3 3/3] tools: introduce parameter > > max_wp_ram_ranges. > > > > Paul Durrant writes ("RE: [Xen-devel] [PATCH v3 3/3] tools: introduce > > parameter max_wp_ram_ranges."): > > > There are patches in the XenGT xen repo which add extra parameters > > > into the VM config to allow libxl to provision a gvt-g instance (of > > > which there are a finite number per GPU) for a VM. The increased > > > limit could be applied when doing so and it may be feasible to > > > determine (maybe from the version of the GPU h/w) what a reasonable > > > limit is. > > > > Right. So in that case there would be no need for this user-visible > > knob (along with its sadly not very helpful documentation) to be > > exposed in the libxl stable API. > > > > No, I really don't think that should be necessary. Libxl merely needs to configure a limit in > the hypervisor appropriate to the gvt-g instance that is provisioned. > Agree. Thanks Kevin