All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Alexander Graf" <agraf@csgraf.de>,
	qemu-arm@nongnu.org,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>
Subject: [PATCH 1/6] target/arm: Only set CPU_INTERRUPT_EXITTB for TCG
Date: Mon, 30 Jun 2025 15:09:32 +0200	[thread overview]
Message-ID: <20250630130937.3487-2-philmd@linaro.org> (raw)
In-Reply-To: <20250630130937.3487-1-philmd@linaro.org>

Commit 34c45d53026 ("target-arm: kvm - re-inject guest debug
exceptions") removed CPU_INTERRUPT_EXITTB from KVM, but it
also appears on HVF. Better to restrict it to TCG.

Suggested-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
---
 target/arm/helper.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/target/arm/helper.c b/target/arm/helper.c
index 889d3088079..764b1f82dc2 100644
--- a/target/arm/helper.c
+++ b/target/arm/helper.c
@@ -10929,7 +10929,7 @@ void arm_cpu_do_interrupt(CPUState *cs)
 
     arm_call_el_change_hook(cpu);
 
-    if (!kvm_enabled()) {
+    if (tcg_enabled()) {
         cs->interrupt_request |= CPU_INTERRUPT_EXITTB;
     }
 }
-- 
2.49.0

  reply	other threads:[~2025-06-30 13:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 13:09 [PATCH 0/6] target/arm: Few accel cleanups Philippe Mathieu-Daudé
2025-06-30 13:09 ` Philippe Mathieu-Daudé [this message]
2025-06-30 13:49   ` [PATCH 1/6] target/arm: Only set CPU_INTERRUPT_EXITTB for TCG Richard Henderson
2025-06-30 16:48   ` Pierrick Bouvier
2025-06-30 13:09 ` [PATCH 2/6] target/arm: Only allow disabling NEON when using TCG Philippe Mathieu-Daudé
2025-06-30 13:51   ` Richard Henderson
2025-06-30 16:49   ` Pierrick Bouvier
2025-07-04 13:03   ` Peter Maydell
2025-07-04 13:17     ` Philippe Mathieu-Daudé
2025-07-04 13:32       ` Peter Maydell
2025-06-30 13:09 ` [PATCH 3/6] target/arm: Better describe PMU depends on TCG or HVF Philippe Mathieu-Daudé
2025-06-30 17:03   ` Pierrick Bouvier
2025-06-30 17:03   ` Pierrick Bouvier
2025-06-30 13:09 ` [PATCH 4/6] target/arm: Re-use arm_is_psci_call() in HVF Philippe Mathieu-Daudé
2025-06-30 13:52   ` Richard Henderson
2025-06-30 16:50   ` Pierrick Bouvier
2025-06-30 13:09 ` [PATCH 5/6] target/arm: Share ARM_PSCI_CALL trace event between TCG and HVF Philippe Mathieu-Daudé
2025-06-30 13:53   ` Richard Henderson
2025-06-30 15:36     ` Philippe Mathieu-Daudé
2025-06-30 16:53   ` Pierrick Bouvier
2025-07-04 13:14     ` Peter Maydell
2025-07-07 14:02       ` Stefan Hajnoczi
2025-07-07 14:12         ` Peter Maydell
2025-07-07 14:08       ` Daniel P. Berrangé
2025-06-30 13:09 ` [PATCH 6/6] target/arm: Allow arm_cpu_tlb_fill_align optionally set CPUTLBEntryFull Philippe Mathieu-Daudé
2025-06-30 13:56   ` Richard Henderson
2025-06-30 15:35     ` Philippe Mathieu-Daudé
2025-06-30 17:00   ` Pierrick Bouvier

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=20250630130937.3487-2-philmd@linaro.org \
    --to=philmd@linaro.org \
    --cc=agraf@csgraf.de \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-arm@nongnu.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 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.