31 Jul
2019
31 Jul
'19
7:16 a.m.
On 30.07.19 21:06, Paolo Bonzini wrote:
On 30/07/19 16:57, Christian Borntraeger wrote:
While this fixes the test (and the migration does work fine), it still means that s390x overindicates the dirty bit for sparsely populated 1M segments. It is just a performance issue, but maybe we should try to get this fixed. Not sure what to do here to remember us about this, adding this as expected fail?
if it's only on the first access after enabling dirty logging, that shouldn't be that bad?
No its not bad, but certainly something to improve if time allows.