qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 07/11] gunyah: Specify device-tree location
Date: Tue, 9 Jan 2024 14:31:03 +0100	[thread overview]
Message-ID: <48ca6b12-6838-4788-8484-90621b46d65f@linaro.org> (raw)
In-Reply-To: <20240109090039.1636383-8-quic_svaddagi@quicinc.com>

Hi Srivatsa,

On 9/1/24 10:00, Srivatsa Vaddagiri wrote:
> Specify the location of device-tree and its size, as Gunyah requires the
> device-tree to be parsed before VM can begin its execution.
> 
> Signed-off-by: Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>
> ---
>   MAINTAINERS               |  1 +
>   accel/stubs/gunyah-stub.c |  5 +++++
>   hw/arm/virt.c             |  6 ++++++
>   include/sysemu/gunyah.h   |  2 ++
>   target/arm/gunyah.c       | 45 +++++++++++++++++++++++++++++++++++++++
>   target/arm/meson.build    |  3 +++
>   6 files changed, 62 insertions(+)
>   create mode 100644 target/arm/gunyah.c

(Please enable scripts/git.orderfile)

> diff --git a/include/sysemu/gunyah.h b/include/sysemu/gunyah.h
> index 4f26938521..a73d17bfb9 100644
> --- a/include/sysemu/gunyah.h
> +++ b/include/sysemu/gunyah.h
> @@ -27,4 +27,6 @@ typedef struct GUNYAHState GUNYAHState;
>   DECLARE_INSTANCE_CHECKER(GUNYAHState, GUNYAH_STATE,
>                            TYPE_GUNYAH_ACCEL)
>   
> +int gunyah_arm_set_dtb(__u64 dtb_start, __u64 dtb_size);
I'm getting:

In file included from hw/intc/arm_gicv3_common.c:35:
include/sysemu/gunyah.h:30:24: error: unknown type name '__u64'
int gunyah_arm_set_dtb(__u64 dtb_start, __u64 dtb_size);
                        ^
include/sysemu/gunyah.h:30:41: error: unknown type name '__u64'
int gunyah_arm_set_dtb(__u64 dtb_start, __u64 dtb_size);
                                         ^
2 errors generated.



  reply	other threads:[~2024-01-09 13:31 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é [this message]
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é
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=48ca6b12-6838-4788-8484-90621b46d65f@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).