All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Leonardo Bras <leobras@redhat.com>,
	Lukas Straub <lukasstraub2@web.de>
Subject: [PATCH 04/13] ram.c: Dont change param->block in the compress thread
Date: Mon,  8 May 2023 17:26:48 +0200	[thread overview]
Message-ID: <20230508152657.66701-5-quintela@redhat.com> (raw)
In-Reply-To: <20230508152657.66701-1-quintela@redhat.com>

From: Lukas Straub <lukasstraub2@web.de>

Instead introduce a extra parameter to trigger the compress thread.
Now, when the compress thread is done, we know what RAMBlock and
offset it did compress.

This will be used in the next commits to move save_page_header()
out of compress code.

Signed-off-by: Lukas Straub <lukasstraub2@web.de>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
---
 migration/ram.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/migration/ram.c b/migration/ram.c
index 7bc05fc034..b552a9e538 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -492,6 +492,7 @@ typedef enum CompressResult CompressResult;
 struct CompressParam {
     bool done;
     bool quit;
+    bool trigger;
     CompressResult result;
     QEMUFile *file;
     QemuMutex mutex;
@@ -565,10 +566,10 @@ static void *do_data_compress(void *opaque)
 
     qemu_mutex_lock(&param->mutex);
     while (!param->quit) {
-        if (param->block) {
+        if (param->trigger) {
             block = param->block;
             offset = param->offset;
-            param->block = NULL;
+            param->trigger = false;
             qemu_mutex_unlock(&param->mutex);
 
             result = do_compress_ram_page(param->file, &param->stream,
@@ -1545,6 +1546,7 @@ static inline void set_compress_params(CompressParam *param, RAMBlock *block,
 {
     param->block = block;
     param->offset = offset;
+    param->trigger = true;
 }
 
 static int compress_page_with_multi_thread(RAMBlock *block, ram_addr_t offset)
-- 
2.40.0



  parent reply	other threads:[~2023-05-08 15:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 15:26 [PATCH 00/13] Migration PULL request (20230508 edition) Juan Quintela
2023-05-08 15:26 ` [PATCH 01/13] qtest/migration-test.c: Add tests with compress enabled Juan Quintela
2023-05-08 15:26 ` [PATCH 02/13] qtest/migration-test.c: Add postcopy " Juan Quintela
2023-05-08 15:26 ` [PATCH 03/13] ram.c: Let the compress threads return a CompressResult enum Juan Quintela
2023-05-08 15:26 ` Juan Quintela [this message]
2023-05-08 15:26 ` [PATCH 05/13] ram.c: Reset result after sending queued data Juan Quintela
2023-05-08 15:26 ` [PATCH 06/13] ram.c: Do not call save_page_header() from compress threads Juan Quintela
2023-05-08 15:26 ` [PATCH 07/13] ram.c: Call update_compress_thread_counts from compress_send_queued_data Juan Quintela
2023-05-08 15:26 ` [PATCH 08/13] ram.c: Remove last ram.c dependency from the core compress code Juan Quintela
2023-05-08 15:26 ` [PATCH 09/13] ram.c: Move core compression code into its own file Juan Quintela
2023-05-08 15:26 ` [PATCH 10/13] ram.c: Move core decompression " Juan Quintela
2023-05-08 15:26 ` [PATCH 11/13] ram compress: Assert that the file buffer matches the result Juan Quintela
2023-05-08 15:26 ` [PATCH 12/13] ram-compress.c: Make target independent Juan Quintela
2023-05-08 15:26 ` [PATCH 13/13] migration: Initialize and cleanup decompression in migration.c Juan Quintela
2023-05-08 16:50 ` [PATCH 00/13] Migration PULL request (20230508 edition) Richard Henderson

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=20230508152657.66701-5-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=leobras@redhat.com \
    --cc=lukasstraub2@web.de \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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.