> From: Paul Durrant [mailto:paul.durr...@citrix.com] > Sent: Thursday, February 04, 2016 11:51 PM > > > -----Original Message----- > > From: Ian Jackson [mailto:ian.jack...@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...@intel.com; Zhang Yu; xen- > > de...@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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
