All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Chaney, Ben" <bchaney@akamai.com>
Cc: David Hildenbrand <david@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"yury-kotov@yandex-team.ru" <yury-kotov@yandex-team.ru>,
	"dgilbert@redhat.com" <dgilbert@redhat.com>,
	"beata.michalska@linaro.org" <beata.michalska@linaro.org>,
	"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
	"alex.bennee@linaro.org" <alex.bennee@linaro.org>,
	"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"junyan.he@intel.com" <junyan.he@intel.com>,
	"imammedo@redhat.com" <imammedo@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"philmd@linaro.org" <philmd@linaro.org>,
	"xiaoguangrong.eric@gmail.com" <xiaoguangrong.eric@gmail.com>,
	"Tottenham, Max" <mtottenh@akamai.com>,
	"Hunt, Joshua" <johunt@akamai.com>,
	"Glasgall, Anna" <aglasgal@akamai.com>,
	"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>
Subject: Re: [Patch] Don't sync volatile memory
Date: Mon, 16 Jun 2025 16:35:18 -0400	[thread overview]
Message-ID: <aFCABp9-h_iBxoKe@x1.local> (raw)
In-Reply-To: <7987BFFC-D46A-4BAB-8973-F30E6689E05F@akamai.com>

On Mon, Jun 16, 2025 at 07:43:02PM +0000, Chaney, Ben wrote:
> Not all pmem regions are backed by non-volatile memory. Syncing volatile
> memory provides no benefit, but can cause performance issues is some
> cases. Only sync memory that is marked as non-volatile.
> 
> Fixes: bd108a44bc29 (migration: ram: Switch to ram block writeback)

Do you plan to work on qemu in the future?  If so, I suggest you go
through this and repost:

https://www.qemu.org/docs/master/devel/submitting-a-patch.html

If the answer is no, I'll at least need your Signed-off-By: line here, then
I can fix all the rest for you.  The patch looks ok though.

Thanks,

> 
> ---
> migration/ram.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/migration/ram.c b/migration/ram.c
> index f25ebd9620..e3ab67acd4 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -3930,7 +3930,9 @@ static int ram_load_cleanup(void *opaque)
>      RAMBlock *rb;
> 
>      RAMBLOCK_FOREACH_NOT_IGNORED(rb) {
> -        qemu_ram_block_writeback(rb);
> +        if (memory_region_is_nonvolatile(rb->mr)) {
> +            qemu_ram_block_writeback(rb);
> +        }
>      }
> 
>      xbzrle_load_cleanup();
> --
> 2.40.1
> 
> 
> 
> 

-- 
Peter Xu



  reply	other threads:[~2025-06-16 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 19:43 [Patch] Don't sync volatile memory Chaney, Ben
2025-06-16 20:35 ` Peter Xu [this message]
2025-06-16 20:59   ` Chaney, Ben

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=aFCABp9-h_iBxoKe@x1.local \
    --to=peterx@redhat.com \
    --cc=aglasgal@akamai.com \
    --cc=alex.bennee@linaro.org \
    --cc=bchaney@akamai.com \
    --cc=beata.michalska@linaro.org \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=johunt@akamai.com \
    --cc=junyan.he@intel.com \
    --cc=mst@redhat.com \
    --cc=mtottenh@akamai.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=xiaoguangrong.eric@gmail.com \
    --cc=yury-kotov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.