qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Daniil Tatianin <d-tatianin@yandex-team.ru>
Cc: Juan Quintela <quintela@redhat.com>,
	Leonardo Bras <leobras@redhat.com>,
	qemu-devel@nongnu.org, yc-core@yandex-team.ru
Subject: Re: [PATCH 0/2] i386/a-b-bootblock: zero the first byte of each page on start
Date: Tue, 26 Sep 2023 17:01:38 -0400	[thread overview]
Message-ID: <ZRNGspuTX84gStfe@x1n> (raw)
In-Reply-To: <20230907192944.1609099-1-d-tatianin@yandex-team.ru>

On Thu, Sep 07, 2023 at 10:29:42PM +0300, Daniil Tatianin wrote:
> This series fixes an issue where the outcome of the migration qtest
> relies on the initial memory contents all being the same across the
> first 100MiB of RAM, which is a very fragile invariant.
> 
> We fix this by making sure we zero the first byte of every testable page
> in range beforehand.

What's the difference between this one and:

https://lore.kernel.org/r/20230907193051.1609310-1-d-tatianin@yandex-team.ru

?

Thanks,

-- 
Peter Xu



      parent reply	other threads:[~2023-09-26 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 19:29 [PATCH 0/2] i386/a-b-bootblock: zero the first byte of each page on start Daniil Tatianin
2023-09-07 19:29 ` [PATCH 1/2] i386/a-b-bootblock: factor test memory addresses out into constants Daniil Tatianin
2023-09-26 20:31   ` Vladimir Sementsov-Ogievskiy
2023-09-07 19:29 ` [PATCH 2/2] i386/a-b-bootblock: zero the first byte of each page on start Daniil Tatianin
2023-09-26 20:41   ` Vladimir Sementsov-Ogievskiy
2023-09-26 21:11     ` Daniil Tatianin
2023-09-26 21:01 ` Peter Xu [this message]

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=ZRNGspuTX84gStfe@x1n \
    --to=peterx@redhat.com \
    --cc=d-tatianin@yandex-team.ru \
    --cc=leobras@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yc-core@yandex-team.ru \
    /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).