On 27/11/15 11:11, Jan Beulich wrote:
On 27.11.15 at 11:57, wrote:
>> On 27/11/15 08:28, Jan Beulich wrote:
>> On 26.11.15 at 17:59, wrote:
Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
commandline-provided masks would take effect in Xen's view of
>>> On 27.11.15 at 11:57, wrote:
> On 27/11/15 08:28, Jan Beulich wrote:
> On 26.11.15 at 17:59, wrote:
>>> Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
>>> commandline-provided masks would take effect in Xen's view of the features.
>>>
>>> As the masks got appl
On 27/11/15 08:28, Jan Beulich wrote:
On 26.11.15 at 17:59, wrote:
>> Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
>> commandline-provided masks would take effect in Xen's view of the features.
>>
>> As the masks got applied after the query for features, the red
>>> On 26.11.15 at 17:59, wrote:
> Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
> commandline-provided masks would take effect in Xen's view of the features.
>
> As the masks got applied after the query for features, the redundant call to
> generic_identify() would
Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
commandline-provided masks would take effect in Xen's view of the features.
As the masks got applied after the query for features, the redundant call to
generic_identify() would clobber the wrong feature information with t
