[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] (v2) Design proposal for RMRR fix

>>> On 14.01.15 at 13:16, <george.dunlap@xxxxxxxxxxxxx> 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).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.