From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>,
peter.maydell@linaro.org, alex.bennee@linaro.org,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: quic_tsoni@quicinc.com, quic_pheragu@quicinc.com,
quic_eberman@quicinc.com, quic_yvasi@quicinc.com,
quic_cvanscha@quicinc.com, quic_mnalajal@quicinc.com
Subject: Re: [RFC/PATCH v1 09/11] gunyah: CPU execution loop
Date: Wed, 10 Jan 2024 16:53:35 +0100 [thread overview]
Message-ID: <a6b05997-cc3f-453c-93a6-66dce2cd9a2e@linaro.org> (raw)
In-Reply-To: <20240109090039.1636383-10-quic_svaddagi@quicinc.com>
Hi Srivatsa,
On 9/1/24 10:00, Srivatsa Vaddagiri wrote:
> Complete the cpu execution loop. At this time, we recognize exits
> associated with only MMIO access. Future patches will add support for
> recognizing other exit reasons, such as PSCI calls made by guest.
>
> Signed-off-by: Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>
> ---
> accel/gunyah/gunyah-accel-ops.c | 7 ++
> accel/gunyah/gunyah-all.c | 201 +++++++++++++++++++++++++++++++-
> include/hw/core/cpu.h | 1 +
> include/sysemu/gunyah_int.h | 9 ++
> target/arm/gunyah.c | 13 +++
> 5 files changed, 230 insertions(+), 1 deletion(-)
> diff --git a/include/hw/core/cpu.h b/include/hw/core/cpu.h
> index 238c02c05e..ef248a658b 100644
> --- a/include/hw/core/cpu.h
> +++ b/include/hw/core/cpu.h
> @@ -371,6 +371,7 @@ struct CPUWatchpoint {
>
> struct KVMState;
> struct kvm_run;
> +struct gh_vcpu_run;
Please do not forward-declare this structure here, it is not required.
>
> /* work queue */
>
> diff --git a/include/sysemu/gunyah_int.h b/include/sysemu/gunyah_int.h
> index dc5b4847a9..72b3027e4e 100644
> --- a/include/sysemu/gunyah_int.h
> +++ b/include/sysemu/gunyah_int.h
> @@ -46,12 +46,21 @@ struct GUNYAHState {
> bool preshmem_reserved;
> uint32_t preshmem_size;
> uint32_t nr_irqs;
> + uint32_t vm_started;
> +};
> +
> +struct AccelCPUState {
> + int fd;
> + struct gh_vcpu_run *run;
> };
>
> int gunyah_create_vm(void);
> +void gunyah_start_vm(void);
> int gunyah_vm_ioctl(int type, ...);
> void *gunyah_cpu_thread_fn(void *arg);
> int gunyah_add_irqfd(int irqfd, int label, Error **errp);
> GUNYAHState *get_gunyah_state(void);
> +int gunyah_arch_put_registers(CPUState *cs, int level);
> +void gunyah_cpu_synchronize_post_reset(CPUState *cpu);
>
> #endif /* GUNYAH_INT_H */
next prev parent reply other threads:[~2024-01-10 15:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 9:00 [RFC/PATCH v1 00/11] Gunyah hypervisor support Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 01/11] gunyah: UAPI header (NOT FOR MERGE) Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 02/11] gunyah: Basic support Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 03/11] gunyah: Add VM properties Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 04/11] gunyah: Support memory assignment Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 05/11] gunyah: Add IRQFD and IOEVENTFD functions Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 06/11] gunyah: Add gicv3 interrupt controller Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 07/11] gunyah: Specify device-tree location Srivatsa Vaddagiri
2024-01-09 13:31 ` Philippe Mathieu-Daudé
2024-01-10 8:34 ` Srivatsa Vaddagiri
2024-01-10 23:07 ` Alex Bennée
2024-01-09 13:36 ` Philippe Mathieu-Daudé
2024-01-10 8:36 ` Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 08/11] gunyah: Customize device-tree Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 09/11] gunyah: CPU execution loop Srivatsa Vaddagiri
2024-01-10 15:49 ` Philippe Mathieu-Daudé
2024-01-10 15:53 ` Philippe Mathieu-Daudé [this message]
2024-01-09 9:00 ` [RFC/PATCH v1 10/11] gunyah: Workarounds (NOT FOR MERGE) Srivatsa Vaddagiri
2024-01-09 9:00 ` [RFC/PATCH v1 11/11] gunyah: Documentation Srivatsa Vaddagiri
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=a6b05997-cc3f-453c-93a6-66dce2cd9a2e@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_cvanscha@quicinc.com \
--cc=quic_eberman@quicinc.com \
--cc=quic_mnalajal@quicinc.com \
--cc=quic_pheragu@quicinc.com \
--cc=quic_svaddagi@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=quic_yvasi@quicinc.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).