qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Weiwei Li" <liweiwei@iscas.ac.cn>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Bin Meng" <bin.meng@windriver.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
	"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-riscv@nongnu.org
Subject: Re: [PATCH 0/2] target/riscv: Only build qemu-system-riscv$$ on rv$$ host
Date: Mon, 3 Jul 2023 12:26:19 +1000	[thread overview]
Message-ID: <CAKmqyKMf9G0cdfphnN2dzUz6taUCRiWwbDSRTrB2ZLO_oix3_w@mail.gmail.com> (raw)
In-Reply-To: <20230627143235.29947-1-philmd@linaro.org>

On Wed, Jun 28, 2023 at 12:33 AM Philippe Mathieu-Daudé
<philmd@linaro.org> wrote:
>
> Per Anup Patel in [*]:
>
>  > Currently, we only support running rv64 guest on rv64 host
>  > and rv32 guest on rv32 host.
>  >
>  > In the future, we might support running rv32 guest on rv64
>  > host but as of now we don't see a strong push for it.
>
> Therefore, when only using the KVM accelerator it is pointless
> to build qemu-system-riscv32 on a rv64 host (or qemu-system-riscv64
> on a rv32 host). Restrict meson to only build the correct binary,
> avoiding to waste ressources building unusable code.
>
> [*] https://lore.kernel.org/qemu-devel/CAAhSdy2JeRHeeoEc1XKQhPO3aDz4YKeyQsPT4S8yKJcYTA+AiQ@mail.gmail.com/
>
> Based-on: <20230626232007.8933-1-philmd@linaro.org>
> "target/riscv: Allow building without TCG (KVM-only so far)"
> https://lore.kernel.org/qemu-devel/20230626232007.8933-1-philmd@linaro.org/
>
> Philippe Mathieu-Daudé (2):
>   target/riscv: Only unify 'riscv32/64' -> 'riscv' for host cpu in meson
>   target/riscv: Only build KVM guest with same wordsize as host

Thanks!

Applied to riscv-to-apply.next

Alistair

>
>  meson.build | 15 +++++++--------
>  1 file changed, 7 insertions(+), 8 deletions(-)
>
> --
> 2.38.1
>
>


      parent reply	other threads:[~2023-07-03  2:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 14:32 [PATCH 0/2] target/riscv: Only build qemu-system-riscv$$ on rv$$ host Philippe Mathieu-Daudé
2023-06-27 14:32 ` [PATCH 1/2] target/riscv: Only unify 'riscv32/64' -> 'riscv' for host cpu in meson Philippe Mathieu-Daudé
2023-06-27 14:32 ` [PATCH 2/2] target/riscv: Only build KVM guest with same wordsize as host Philippe Mathieu-Daudé
2023-06-28  7:48 ` [PATCH 0/2] target/riscv: Only build qemu-system-riscv$$ on rv$$ host Richard Henderson
2023-06-28  7:55 ` Philippe Mathieu-Daudé
2023-07-03  2:24 ` Alistair Francis
2023-07-03  2:26 ` Alistair Francis [this message]

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=CAKmqyKMf9G0cdfphnN2dzUz6taUCRiWwbDSRTrB2ZLO_oix3_w@mail.gmail.com \
    --to=alistair23@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=berrange@redhat.com \
    --cc=bin.meng@windriver.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=liweiwei@iscas.ac.cn \
    --cc=marcandre.lureau@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=zhiwei_liu@linux.alibaba.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).