From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: xianglai li <lixianglai@loongson.cn>, qemu-devel@nongnu.org
Cc: gaosong@loongson.cn, maobibo@loongson.cn,
zhaotianrui@loongson.cn, mst@redhat.com, cohuck@redhat.com,
pbonzini@redhat.com, marcandre.lureau@redhat.com,
berrange@redhat.com, thuth@redhat.com,
richard.henderson@linaro.org, peter.maydell@linaro.org,
yangxiaojuan@loongson.cn
Subject: Re: [PATCH v1 8/9] target/loongarch: Implement set vcpu intr for kvm
Date: Wed, 8 Nov 2023 10:53:04 +0100 [thread overview]
Message-ID: <cb819430-74b2-46e5-a375-9ef1a0dae645@linaro.org> (raw)
In-Reply-To: <20231108014141.2590657-9-lixianglai@loongson.cn>
On 8/11/23 02:41, xianglai li wrote:
> From: Tianrui Zhao <zhaotianrui@loongson.cn>
>
> Implement loongarch kvm set vcpu interrupt interface,
> when a irq is set in vcpu, we use the KVM_INTERRUPT
> ioctl to set intr into kvm.
>
> Signed-off-by: Tianrui Zhao <zhaotianrui@loongson.cn>
> Signed-off-by: xianglai li <lixianglai@loongson.cn>
> ---
> target/loongarch/cpu.c | 18 +++++++++++++-----
> target/loongarch/kvm-stub.c | 13 +++++++++++++
> target/loongarch/kvm.c | 15 +++++++++++++++
> target/loongarch/kvm_loongarch.h | 13 +++++++++++++
> target/loongarch/trace-events | 1 +
> 5 files changed, 55 insertions(+), 5 deletions(-)
> create mode 100644 target/loongarch/kvm-stub.c
> create mode 100644 target/loongarch/kvm_loongarch.h
>
> diff --git a/target/loongarch/cpu.c b/target/loongarch/cpu.c
> index 0a4d1a9778..3073f1548d 100644
> --- a/target/loongarch/cpu.c
> +++ b/target/loongarch/cpu.c
> @@ -20,6 +20,11 @@
> #include "sysemu/reset.h"
> #include "tcg/tcg.h"
> #include "vec.h"
> +#include "sysemu/kvm.h"
> +#include "kvm_loongarch.h"
> +#ifdef CONFIG_KVM
> +#include <linux/kvm.h>
> +#endif
>
> const char * const regnames[32] = {
> "r0", "r1", "r2", "r3", "r4", "r5", "r6", "r7",
> @@ -108,12 +113,15 @@ void loongarch_cpu_set_irq(void *opaque, int irq, int level)
> return;
> }
>
> - env->CSR_ESTAT = deposit64(env->CSR_ESTAT, irq, 1, level != 0);
> -
> - if (FIELD_EX64(env->CSR_ESTAT, CSR_ESTAT, IS)) {
> - cpu_interrupt(cs, CPU_INTERRUPT_HARD);
> + if (kvm_enabled()) {
> + kvm_loongarch_set_interrupt(cpu, irq, level);
Since you guard this call with kvm_enabled(), ...
> } else {
> - cpu_reset_interrupt(cs, CPU_INTERRUPT_HARD);
> + env->CSR_ESTAT = deposit64(env->CSR_ESTAT, irq, 1, level != 0);
> + if (FIELD_EX64(env->CSR_ESTAT, CSR_ESTAT, IS)) {
> + cpu_interrupt(cs, CPU_INTERRUPT_HARD);
> + } else {
> + cpu_reset_interrupt(cs, CPU_INTERRUPT_HARD);
> + }
> }
> }
>
> diff --git a/target/loongarch/kvm-stub.c b/target/loongarch/kvm-stub.c
> new file mode 100644
> index 0000000000..d38c30ec78
> --- /dev/null
> +++ b/target/loongarch/kvm-stub.c
> @@ -0,0 +1,13 @@
> +/*
> + * QEMU KVM LoongArch specific function stubs
> + *
> + * Copyright (c) 2023 Loongson Technology Corporation Limited
> + */
> +#include "qemu/osdep.h"
> +#include "cpu.h"
> +#include "kvm_loongarch.h"
> +
> +int kvm_loongarch_set_interrupt(LoongArchCPU *cpu, int irq, int level)
> +{
> + g_assert_not_reached();
... this stub shouldn't be required.
Have you tested a TCG-only build? Then a KVM-only one?
> +}
> diff --git a/target/loongarch/kvm_loongarch.h b/target/loongarch/kvm_loongarch.h
> new file mode 100644
> index 0000000000..cdef980eec
> --- /dev/null
> +++ b/target/loongarch/kvm_loongarch.h
> @@ -0,0 +1,13 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */
> +/*
> + * QEMU LoongArch kvm interface
> + *
> + * Copyright (c) 2023 Loongson Technology Corporation Limited
> + */
> +
> +#ifndef QEMU_KVM_LOONGARCH_H
> +#define QEMU_KVM_LOONGARCH_H
> +
Missing:
#include "cpu.h"
to get the LoongArchCPU type declaration.
> +int kvm_loongarch_set_interrupt(LoongArchCPU *cpu, int irq, int level);
> +
> +#endif
Regards,
Phil.
next prev parent reply other threads:[~2023-11-08 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 1:41 [PATCH v1 0/9] Add loongarch kvm accel support xianglai li
2023-11-08 1:41 ` [PATCH v1 1/9] linux-headers: Add KVM headers for loongarch xianglai li
2023-11-08 9:57 ` Cornelia Huck
2023-11-08 1:41 ` [PATCH v1 2/9] target/loongarch: Define some kvm_arch interfaces xianglai li
2023-11-08 1:41 ` [PATCH v1 3/9] target/loongarch: Supplement vcpu env initial when vcpu reset xianglai li
2023-11-08 1:41 ` [PATCH v1 4/9] target/loongarch: Implement kvm get/set registers xianglai li
2023-11-08 9:48 ` Philippe Mathieu-Daudé
2023-11-08 1:41 ` [PATCH v1 5/9] target/loongarch: Implement kvm_arch_init function xianglai li
2023-11-08 1:41 ` [PATCH v1 6/9] target/loongarch: Implement kvm_arch_init_vcpu xianglai li
2023-11-08 1:41 ` [PATCH v1 7/9] target/loongarch: Implement kvm_arch_handle_exit xianglai li
2023-11-08 1:41 ` [PATCH v1 8/9] target/loongarch: Implement set vcpu intr for kvm xianglai li
2023-11-08 9:53 ` Philippe Mathieu-Daudé [this message]
2023-11-08 1:41 ` [PATCH v1 9/9] target/loongarch: Add loongarch kvm into meson build xianglai li
2023-11-08 18:42 ` 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=cb819430-74b2-46e5-a375-9ef1a0dae645@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=gaosong@loongson.cn \
--cc=lixianglai@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=yangxiaojuan@loongson.cn \
--cc=zhaotianrui@loongson.cn \
/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).