On 14.08.19 12:44, Alex Bennée wrote:
>
> David Hildenbrand writes:
>
>> On 14.08.19 12:06, Alex Bennée wrote:
>>>
>>> David Hildenbrand writes:
>>>
Whenever we modify a storage key, we shuld flush the TLBs of all CPUs,
so the MMU fault handling code can properly consider the changed
David Hildenbrand writes:
> On 14.08.19 12:06, Alex Bennée wrote:
>>
>> David Hildenbrand writes:
>>
>>> Whenever we modify a storage key, we shuld flush the TLBs of all CPUs,
>>> so the MMU fault handling code can properly consider the changed storage
>>> key (to e.g., properly set the refere
On 14.08.19 12:06, Alex Bennée wrote:
>
> David Hildenbrand writes:
>
>> Whenever we modify a storage key, we shuld flush the TLBs of all CPUs,
>> so the MMU fault handling code can properly consider the changed storage
>> key (to e.g., properly set the reference and change bit on the next
>> ac
David Hildenbrand writes:
> Whenever we modify a storage key, we shuld flush the TLBs of all CPUs,
> so the MMU fault handling code can properly consider the changed storage
> key (to e.g., properly set the reference and change bit on the next
> accesses).
>
> These functions are barely used in
Whenever we modify a storage key, we shuld flush the TLBs of all CPUs,
so the MMU fault handling code can properly consider the changed storage
key (to e.g., properly set the reference and change bit on the next
accesses).
These functions are barely used in modern Linux guests, so the performance
