>>> On 10.08.18 at 11:49, wrote:
> On 10/08/2018 09:08, Jan Beulich wrote:
> On 09.08.18 at 18:38, wrote:
>>> As it currently stands, 'xpti=dom0' is indistinguishable from the default
>>> value, which means it will be overridden by ARCH_CAPABILITIES_RDCL_NO on
> fixed
>>> hardware.
>>>
>>> S
On 10/08/2018 09:08, Jan Beulich wrote:
On 09.08.18 at 18:38, wrote:
>> As it currently stands, 'xpti=dom0' is indistinguishable from the default
>> value, which means it will be overridden by ARCH_CAPABILITIES_RDCL_NO on
>> fixed
>> hardware.
>>
>> Switch opt_xpti to use -1 as a default lik
>>> On 09.08.18 at 18:38, wrote:
> As it currently stands, 'xpti=dom0' is indistinguishable from the default
> value, which means it will be overridden by ARCH_CAPABILITIES_RDCL_NO on fixed
> hardware.
>
> Switch opt_xpti to use -1 as a default like all our other related options, and
> clobber it
On 09/08/18 18:38, Andrew Cooper wrote:
> As it currently stands, 'xpti=dom0' is indistinguishable from the default
> value, which means it will be overridden by ARCH_CAPABILITIES_RDCL_NO on fixed
> hardware.
>
> Switch opt_xpti to use -1 as a default like all our other related options, and
> clob
As it currently stands, 'xpti=dom0' is indistinguishable from the default
value, which means it will be overridden by ARCH_CAPABILITIES_RDCL_NO on fixed
hardware.
Switch opt_xpti to use -1 as a default like all our other related options, and
clobber it as soon as we have a string to parse.
In add
