[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3092bab6-8ab9-c404-a5bb-64ca89eccd12@redhat.com>
Date: Tue, 30 Jul 2019 13:35:21 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Thomas Huth <thuth@...hat.com>, kvm@...r.kernel.org,
Christian Borntraeger <borntraeger@...ibm.com>,
Janosch Frank <frankja@...ux.ibm.com>
Cc: linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, David Hildenbrand <david@...hat.com>,
Cornelia Huck <cohuck@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Shuah Khan <shuah@...nel.org>, Peter Xu <peterx@...hat.com>
Subject: Re: [PATCH 2/2] KVM: selftests: Enable dirty_log_test on s390x
On 30/07/19 12:01, Thomas Huth wrote:
> +#ifdef __s390x__
> + /*
> + * On s390x, all pages of a 1M segment are initially marked as dirty
> + * when a page of the segment is written to for the very first time.
> + * To compensate this specialty in this test, we need to touch all
> + * pages during the first iteration.
> + */
> + for (i = 0; i < guest_num_pages; i++) {
> + addr = guest_test_virt_mem + i * guest_page_size;
> + *(uint64_t *)addr = READ_ONCE(iteration);
> + }
> +#endif
Go ahead and make this unconditional.
Paolo
Powered by blists - more mailing lists