qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Daniil Tatianin <d-tatianin@yandex-team.ru>
Cc: Peter Xu <peterx@redhat.com>,  Leonardo Bras <leobras@redhat.com>,
	qemu-devel@nongnu.org,  qemu-s390x@nongnu.org
Subject: Re: [PATCH v2 2/3] i386/a-b-bootblock: zero the first byte of each page on start
Date: Wed, 04 Oct 2023 10:53:34 +0200	[thread overview]
Message-ID: <87o7he4vld.fsf@secure.mitica> (raw)
In-Reply-To: <20230919102346.2117963-3-d-tatianin@yandex-team.ru> (Daniil Tatianin's message of "Tue, 19 Sep 2023 13:23:45 +0300")

Daniil Tatianin <d-tatianin@yandex-team.ru> wrote:
> The migration qtest all the way up to this point used to work by sheer
> luck relying on the contents of all pages from 1MiB to 100MiB to contain
> the same one value in the first byte initially.
>
> This easily breaks if we reduce the amount of RAM for the test instances
> from 150MiB to e.g 110MiB since that makes SeaBIOS dirty some of the
> pages starting at about 0x5dd2000 (~93 MiB) as it reuses those for the
> HighMemory allocator since commit dc88f9b72df ("malloc: use large
> ZoneHigh when there is enough memory").
>
> This would result in the following errors:
>     12/60 qemu:qtest+qtest-x86_64 / qtest-x86_64/migration-test                 ERROR           2.74s   killed by signal 6 SIGABRT
>     stderr:
>     Memory content inconsistency at 5dd2000 first_byte = cc last_byte = cb current = 9e hit_edge = 1
>     Memory content inconsistency at 5dd3000 first_byte = cc last_byte = cb current = 89 hit_edge = 1
>     Memory content inconsistency at 5dd4000 first_byte = cc last_byte = cb current = 23 hit_edge = 1
>     Memory content inconsistency at 5dd5000 first_byte = cc last_byte = cb current = 31 hit_edge = 1
>     Memory content inconsistency at 5dd6000 first_byte = cc last_byte = cb current = 70 hit_edge = 1
>     Memory content inconsistency at 5dd7000 first_byte = cc last_byte = cb current = ff hit_edge = 1
>     Memory content inconsistency at 5dd8000 first_byte = cc last_byte = cb current = 54 hit_edge = 1
>     Memory content inconsistency at 5dd9000 first_byte = cc last_byte = cb current = 64 hit_edge = 1
>     Memory content inconsistency at 5dda000 first_byte = cc last_byte = cb current = 1d hit_edge = 1
>     Memory content inconsistency at 5ddb000 first_byte = cc last_byte = cb current = 1a hit_edge = 1
>     and in another 26 pages**
>     ERROR:../tests/qtest/migration-test.c:300:check_guests_ram: assertion failed: (bad == 0)
>
> Fix this by always zeroing the first byte of each page in the range so
> that we get consistent results no matter the initial contents.
>
> Fixes: ea0c6d62391 ("test: Postcopy")
> Signed-off-by: Daniil Tatianin <d-tatianin@yandex-team.ru>
> Reviewed-by: Peter Xu <peterx@redhat.com>
> ---

Reviewed-by: Juan Quintela <quintela@redhat.com>

queued.



  parent reply	other threads:[~2023-10-04  8:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 10:23 [PATCH v2 0/3] migration-qtest: zero the first byte of each page on start Daniil Tatianin
2023-09-19 10:23 ` [PATCH v2 1/3] i386/a-b-bootblock: factor test memory addresses out into constants Daniil Tatianin
2023-09-26 21:22   ` Vladimir Sementsov-Ogievskiy
2023-10-02  7:24   ` Daniil Tatianin
2023-10-04  8:50   ` Juan Quintela
2023-09-19 10:23 ` [PATCH v2 2/3] i386/a-b-bootblock: zero the first byte of each page on start Daniil Tatianin
2023-09-26 21:23   ` Vladimir Sementsov-Ogievskiy
2023-10-04  8:53   ` Juan Quintela [this message]
2023-09-19 10:23 ` [PATCH v2 3/3] s390x/a-b-bios: " Daniil Tatianin
2023-09-26 21:25   ` Vladimir Sementsov-Ogievskiy
2023-10-04  8:53   ` Juan Quintela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7he4vld.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=d-tatianin@yandex-team.ru \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).