From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: (v2) Design proposal for RMRR fix Date: Wed, 14 Jan 2015 18:16:19 +0000 Message-ID: <54B6B273.4060009@eu.citrix.com> References: <54B3AE8802000078000539B7@mail.emea.novell.com> <54B515E6020000780005444A@mail.emea.novell.com> <54B54D48020000780005473E@mail.emea.novell.com> <54B540AA.1010905@eu.citrix.com> <54B63E250200007800054A36@mail.emea.novell.com> <54B65E24.4020004@eu.citrix.com> <54B68DBB0200007800054EC6@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54B68DBB0200007800054EC6@mail.emea.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.liu2@citrix.com" , "ian.campbell@citrix.com" , "stefano.stabellini@eu.citrix.com" , "tim@xen.org" , "ian.jackson@eu.citrix.com" , "xen-devel@lists.xen.org" , Yang Z Zhang , Tiejun Chen List-Id: xen-devel@lists.xenproject.org On 01/14/2015 02:39 PM, Jan Beulich wrote: >>>> On 14.01.15 at 13:16, wrote: >> On 01/14/2015 09:43 AM, Tian, Kevin wrote: >>> for other usages like hotplug/migration: >>> reserved_regions = [ 'host, 0/1', 'start, end, 0/1', 'start, end, 0/1', ...] >>> If 'host' is specified, it implies rmrr_host, besides user can specific >>> explicit ranges according to his detail requirement. >>> >>> based on above configuration interface, libxl can construct necessary >>> reserve regions with individual try/force policies. >> >> Same here; I'd do something like: >> >> rmrr = [ "0xe0000:0xeffff,check=try", "0xa000000:0xa0000fff" ] >> >> Where here the first one would be allowed to conflict in the domain >> builder; but the second would error out if it couldn't be made for some >> reason. > > Just to avoid confusion - I continue to think that the try flag on > explicitly specified regions makes no sense, i.e. I'd see only > something like > >> rmrr = [ "host,check=try", "0xe0000:0xeffff", "0xa000000:0xa0000fff" ] > > as viable (with the token "check" not necessarily being the most > expressive one for the purpose it has). OK -- this is a fairly minor detail that we can discuss when the patches are actually submitted. -George