From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Cameron Esfahani <dirty@apple.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Roman Bolshakov <rbolshakov@ddn.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] accel: Do not set CPUState::can_do_io in non-TCG accels
Date: Thu, 30 Nov 2023 07:51:14 -0600 [thread overview]
Message-ID: <768e7409-62a7-441c-960d-dc99ab89c7d0@linaro.org> (raw)
In-Reply-To: <20231129205037.16849-1-philmd@linaro.org>
On 11/29/23 14:50, Philippe Mathieu-Daudé wrote:
> 'can_do_io' is specific to TCG. Having it set in non-TCG
> code is confusing, so remove it from QTest / HVF / KVM.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> accel/dummy-cpus.c | 1 -
> accel/hvf/hvf-accel-ops.c | 1 -
> accel/kvm/kvm-accel-ops.c | 1 -
> 3 files changed, 3 deletions(-)
>
> diff --git a/accel/dummy-cpus.c b/accel/dummy-cpus.c
> index b75c919ac3..1005ec6f56 100644
> --- a/accel/dummy-cpus.c
> +++ b/accel/dummy-cpus.c
> @@ -27,7 +27,6 @@ static void *dummy_cpu_thread_fn(void *arg)
> qemu_mutex_lock_iothread();
> qemu_thread_get_self(cpu->thread);
> cpu->thread_id = qemu_get_thread_id();
> - cpu->neg.can_do_io = true;
> current_cpu = cpu;
I expect this is ok...
When I was moving this variable around just recently, 464dacf6, I wondered about these
other settings, and I wondered if they used to be required for implementing some i/o on
behalf of hw accel. Something that has now been factored out to e.g. kvm_handle_io, which
now uses address_space_rw directly.
I see 3 reads of can_do_io: accel/tcg/{cputlb.c, icount-common.c} and system/watchpoint.c.
The final one is nested within replay_running_debug(), which implies icount and tcg.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
>
> #ifndef _WIN32
> diff --git a/accel/hvf/hvf-accel-ops.c b/accel/hvf/hvf-accel-ops.c
> index abe7adf7ee..2bba54cf70 100644
> --- a/accel/hvf/hvf-accel-ops.c
> +++ b/accel/hvf/hvf-accel-ops.c
> @@ -428,7 +428,6 @@ static void *hvf_cpu_thread_fn(void *arg)
> qemu_thread_get_self(cpu->thread);
>
> cpu->thread_id = qemu_get_thread_id();
> - cpu->neg.can_do_io = true;
> current_cpu = cpu;
>
> hvf_init_vcpu(cpu);
> diff --git a/accel/kvm/kvm-accel-ops.c b/accel/kvm/kvm-accel-ops.c
> index 6195150a0b..f273f415db 100644
> --- a/accel/kvm/kvm-accel-ops.c
> +++ b/accel/kvm/kvm-accel-ops.c
> @@ -36,7 +36,6 @@ static void *kvm_vcpu_thread_fn(void *arg)
> qemu_mutex_lock_iothread();
> qemu_thread_get_self(cpu->thread);
> cpu->thread_id = qemu_get_thread_id();
> - cpu->neg.can_do_io = true;
> current_cpu = cpu;
>
> r = kvm_init_vcpu(cpu, &error_fatal);
next prev parent reply other threads:[~2023-11-30 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 20:50 [PATCH] accel: Do not set CPUState::can_do_io in non-TCG accels Philippe Mathieu-Daudé
2023-11-30 12:48 ` Claudio Fontana
2023-11-30 13:31 ` Philippe Mathieu-Daudé
2023-11-30 13:37 ` Claudio Fontana
2023-11-30 13:51 ` Richard Henderson [this message]
2024-01-16 21:24 ` Philippe Mathieu-Daudé
2024-01-17 9:39 ` Philippe Mathieu-Daudé
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=768e7409-62a7-441c-960d-dc99ab89c7d0@linaro.org \
--to=richard.henderson@linaro.org \
--cc=dirty@apple.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rbolshakov@ddn.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 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).