qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Alexandre Iooss" <erdnaxe@crans.org>,
	"Mahmoud Mandour" <ma.mandourr@gmail.com>
Subject: [PULL 17/29] plugins: fix order of init/idle/resume callback
Date: Wed, 28 Feb 2024 11:56:49 +0000	[thread overview]
Message-ID: <20240228115701.1416107-18-alex.bennee@linaro.org> (raw)
In-Reply-To: <20240228115701.1416107-1-alex.bennee@linaro.org>

From: Pierrick Bouvier <pierrick.bouvier@linaro.org>

We found that vcpu_init_hook was called *after* idle callback.
vcpu_init is called from cpu_realize_fn, while idle/resume cb are called
from qemu_wait_io_event (in vcpu thread).

This change ensures we only call idle and resume cb only once a plugin
was init for a given vcpu.

Next change in the series will run vcpu_init asynchronously, which will
make it run *after* resume callback as well. So we fix this now.

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Message-Id: <20240213094009.150349-4-pierrick.bouvier@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20240227144335.1196131-18-alex.bennee@linaro.org>

diff --git a/plugins/core.c b/plugins/core.c
index caa66311351..2392bbb8889 100644
--- a/plugins/core.c
+++ b/plugins/core.c
@@ -391,12 +391,17 @@ void qemu_plugin_vcpu_syscall_ret(CPUState *cpu, int64_t num, int64_t ret)
 
 void qemu_plugin_vcpu_idle_cb(CPUState *cpu)
 {
-    plugin_vcpu_cb__simple(cpu, QEMU_PLUGIN_EV_VCPU_IDLE);
+    /* idle and resume cb may be called before init, ignore in this case */
+    if (cpu->cpu_index < plugin.num_vcpus) {
+        plugin_vcpu_cb__simple(cpu, QEMU_PLUGIN_EV_VCPU_IDLE);
+    }
 }
 
 void qemu_plugin_vcpu_resume_cb(CPUState *cpu)
 {
-    plugin_vcpu_cb__simple(cpu, QEMU_PLUGIN_EV_VCPU_RESUME);
+    if (cpu->cpu_index < plugin.num_vcpus) {
+        plugin_vcpu_cb__simple(cpu, QEMU_PLUGIN_EV_VCPU_RESUME);
+    }
 }
 
 void qemu_plugin_register_vcpu_idle_cb(qemu_plugin_id_t id,
-- 
2.39.2



  parent reply	other threads:[~2024-02-28 12:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 11:56 [PULL 00/29] testing, gdbstub and plugin updates Alex Bennée
2024-02-28 11:56 ` [PULL 01/29] tests/tcg: update licenses to GPLv2 as intended Alex Bennée
2024-02-28 11:56 ` [PULL 02/29] tests/tcg: bump TCG test timeout to 120s Alex Bennée
2024-02-28 11:56 ` [PULL 03/29] tests/vm: avoid re-building the VM images all the time Alex Bennée
2024-02-28 11:56 ` [PULL 04/29] tests/vm: update openbsd image to 7.4 Alex Bennée
2024-02-28 11:56 ` [PULL 05/29] target/arm: Use GDBFeature for dynamic XML Alex Bennée
2024-02-28 11:56 ` [PULL 06/29] target/ppc: " Alex Bennée
2024-02-28 11:56 ` [PULL 07/29] target/riscv: " Alex Bennée
2024-02-28 11:56 ` [PULL 08/29] gdbstub: Use GDBFeature for gdb_register_coprocessor Alex Bennée
2024-02-28 11:56 ` [PULL 09/29] gdbstub: Use GDBFeature for GDBRegisterState Alex Bennée
2024-02-28 11:56 ` [PULL 10/29] gdbstub: Change gdb_get_reg_cb and gdb_set_reg_cb Alex Bennée
2024-02-28 11:56 ` [PULL 11/29] gdbstub: Simplify XML lookup Alex Bennée
2024-02-28 11:56 ` [PULL 12/29] gdbstub: Infer number of core registers from XML Alex Bennée
2024-02-28 11:56 ` [PULL 13/29] hw/core/cpu: Remove gdb_get_dynamic_xml member Alex Bennée
2024-02-28 11:56 ` [PULL 14/29] gdbstub: Add members to identify registers to GDBFeature Alex Bennée
2024-02-28 11:56 ` [PULL 15/29] plugins: remove previous n_vcpus functions from API Alex Bennée
2024-02-28 11:56 ` [PULL 16/29] plugins: add qemu_plugin_num_vcpus function Alex Bennée
2024-02-28 11:56 ` Alex Bennée [this message]
2024-02-28 11:56 ` [PULL 18/29] linux-user: ensure nios2 processes queued work Alex Bennée
2024-02-28 11:56 ` [PULL 19/29] cpu: call plugin init hook asynchronously Alex Bennée
2024-02-28 11:56 ` [PULL 20/29] plugins: Use different helpers when reading registers Alex Bennée
2024-02-28 11:56 ` [PULL 21/29] gdbstub: expose api to find registers Alex Bennée
2024-02-28 11:56 ` [PULL 22/29] plugins: create CPUPluginState and migrate plugin_mask Alex Bennée
2024-02-28 11:56 ` [PULL 23/29] plugins: add an API to read registers Alex Bennée
2024-02-28 11:56 ` [PULL 24/29] tests/tcg: expand insn test case to exercise register API Alex Bennée
2024-02-28 11:56 ` [PULL 25/29] contrib/plugins: fix imatch Alex Bennée
2024-02-28 11:56 ` [PULL 26/29] contrib/plugins: extend execlog to track register changes Alex Bennée
2024-03-01  7:19   ` Zhao Liu
2024-03-01 10:22     ` Alex Bennée
2024-03-01 15:54       ` Zhao Liu
2024-03-01 16:30         ` Alex Bennée
2024-03-02  7:02           ` Zhao Liu
2024-03-08 13:21   ` Peter Maydell
2024-02-28 11:56 ` [PULL 27/29] docs/devel: lift example and plugin API sections up Alex Bennée
2024-02-28 11:57 ` [PULL 28/29] docs/devel: document some plugin assumptions Alex Bennée
2024-02-28 11:57 ` [PULL 29/29] docs/devel: plugins can trigger a tb flush Alex Bennée
2024-02-28 17:26 ` [PULL 00/29] testing, gdbstub and plugin updates Peter Maydell

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=20240228115701.1416107-18-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=erdnaxe@crans.org \
    --cc=ma.mandourr@gmail.com \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).