[PATCH RFC 1/1] qemu: capabilities: disable csske for host cpu

[David Hildenbrand]

On 11.03.22 13:54, Christian Borntraeger wrote:
> Am 11.03.22 um 13:27 schrieb David Hildenbrand:
>> On 11.03.22 13:12, Christian Borntraeger wrote:
>>>
>>>
>>> Am 11.03.22 um 10:23 schrieb David Hildenbrand:
>>>> On 11.03.22 10:17, Daniel P. Berrangé wrote:
>>>>> On Thu, Mar 10, 2022 at 11:17:38PM -0500, Collin Walling wrote:
>>>>>> CPU models past gen16a will no longer support the csske feature. In
>>>>>> order to secure migration of guests running on machines that still
>>>>>> support this feature to machines that do not, let's disable csske
>>>>>> in the host-model.
>>>>
>>>> Sorry to say, removing CPU features is a no-go when wanting to guarantee
>>>> forward migration without taking care about CPU model details manually
>>>> and simply using the host model. Self-made HW vendor problem.
>>>
>>> And this simply does not reflect reality. Intel and Power have removed TX
>>> for example. We can now sit back and please ourselves how we live in our
>>> world of dreams. Or we can try to define an interface that deals with
>>> reality and actually solves problems.
>>>
>>
>> Ehm, so, I spell out the obvious and get such a reaction? Okay, thank you.
> 
> Sorry, reading my writing again shows that I clearly miscommunicated in a
> very bad style. My point was rather trying to solve a problem instead
> I wrote something up in a hurry which resulted in something offensive.
> 
> Please accept my apologies.
> 

No hard feelings, I understand that this is an important thing to sort
out for IBM.

-- 
Thanks,

David / dhildenb