From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B8D88C36010 for ; Fri, 11 Apr 2025 14:37:31 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1u3FUd-0001j2-NB; Fri, 11 Apr 2025 10:36:31 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1u3FUb-0001iD-Bz; Fri, 11 Apr 2025 10:36:29 -0400 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1u3FUZ-0001nK-By; Fri, 11 Apr 2025 10:36:29 -0400 Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-5e5cded3e2eso3271176a12.0; Fri, 11 Apr 2025 07:36:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744382184; x=1744986984; darn=nongnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TlF6NDZu6E7cqFh7Nc+T41PatugtSHL1p7nnfIPlLdk=; b=fI8U9exj3KvkMK8FxiWNqjTZ39cE0eN34pep+s2z8Hr8jVWPI0qndzDAhSI8kXwVY3 NQ41D5a6ugUSaSWMSqnE+xQsNAXA+PIH1aj6Pq7R1Bp5A8XGnlAIts+sV2J4WJpOzm4Z 1xuDcetKMzkMa9EqoPbXg2ks8/i4zljnX65Q1W/2tkqO70t1bf1LnV8ja/VwApD1ooVy MblECbNLxvHTmuSRBAAaneSNZWw+8uraTpDkGtQCza/KKY42ufhMv+vPqc+O/Y3cRww2 6iUp6gNpHeNb6YtnDBfMKD5j0hlLNc0+S1YDsgvp8rSId7FWSAS2Y48Q1lgSyLeZGqcm vGig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744382184; x=1744986984; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TlF6NDZu6E7cqFh7Nc+T41PatugtSHL1p7nnfIPlLdk=; b=wSJFS4KPYxTlFCYA7tRk1fJK/8iFlpbuZq3jAt1n/lS4wxhOIiZQD+6f8sscwrG106 VBSM2hKQQ/Wvta6i6PQEUG2IvUEqr+GVpcMM81L/IWGgueWCuktGjcWb4SZ3IUB6GC3K zFlN0tYMMbH1cBKg4itOgDocRvbjY/0DUZfmVuPVxUVXVuDJzibjaPsk83f/KNWg5yaI F4D6yJGJOSZ9apJWkPtFgMNRKl0yzud0Mb/JdB+195FjYhDmQbCh00sTNMFT2LEPykf9 HRwe5+ogtZ4fhG4oAvUTVIRd2uXN+o5cKaQ6UVLpCUnYcK1y3DpyvvDzBJVNUZC57LBR 8k0g== X-Forwarded-Encrypted: i=1; AJvYcCW7Y5NJfe9KIht0ses3EhAmty4kCVx+x1RbevAS1uQJUx+m0VouuerT5zbgL+5fKwzfYQs2IMoBLqxj/g==@nongnu.org, AJvYcCWn4Ew03mZzaC0yp14Q/QdaIrDsh8E73lxWGBM5loe9BmQWOkqafT+giwfZj+Cni60V9NFhsZrMaA==@nongnu.org, AJvYcCXOtmfa5VurI/3OCSYeSvfFENlUTM1mKMJYsjyf8UZ6FLaAnm2N+SGo8qlz8zEPTcC/sH1vSjCHwJvIFg==@nongnu.org, AJvYcCXo4TlJC4x0M5ewXswqPFv4smk/jXz92IZ5gUDeNOy4gyrk0z0z2cwVM+g7zGqL/Ez0eoPuEPZydqQcwA==@nongnu.org X-Gm-Message-State: AOJu0YxRV7RToOzN6m8EnuoHgoAGfXaoRLZlebkln6UaGPqEot5Hrf7d dVu7Y/RWuz07HiG2FsTh4bobS3yRIRSg676TRVkeUYAAAPEeYSjgoLDJkeinO5zKvmGY0sMe/p2 G3Hy9eaxbBMsIFVIwGpDDGC+Y1HQ= X-Gm-Gg: ASbGncusPzVB7rXYhg4FEKrnvdZmI5mBT/TG/sCacXQEIx7oSgv1MJ+I/YlirC79tDO DzWp+1cOPXD4sdBLJbR7TMBWAQnpuqxOzmvX8hiRyfSs1MIf2S7GDG68KnyTB1gPTPI4NBnsJUC 85rX5gWjy/WpnBY4WpC4KVYOwaAlAATUQQ1e+WhG55ogboYDxLtsw= X-Google-Smtp-Source: AGHT+IEK4IlWPqik4XVDKLNC42CRTXGG0nCurAmChUtUb3OKn1+5+1bmiQVlarf1wzo4Olhm09ujK8nS6X9rvaZgqTI= X-Received: by 2002:a17:906:3551:b0:aca:d4f6:440d with SMTP id a640c23a62f3a-acad4f64472mr203284666b.17.1744382183784; Fri, 11 Apr 2025 07:36:23 -0700 (PDT) MIME-Version: 1.0 References: <20250409192115.GA5528@fedora> <83f44749-0eea-48f0-8aa5-3882132e30d0@linaro.org> In-Reply-To: <83f44749-0eea-48f0-8aa5-3882132e30d0@linaro.org> From: Kohei Tokunaga Date: Fri, 11 Apr 2025 23:36:10 +0900 X-Gm-Features: ATxdqUG2wUVfL0Bc-xKm6Ed3L3KzqObfzFH1fQHjiBHOvWTFvTqQyENfOv92ae8 Message-ID: Subject: Re: [PATCH 00/10] Enable QEMU to run on browsers To: Pierrick Bouvier , qemu-devel@nongnu.org Cc: =?UTF-8?Q?Philippe_Mathieu=2DDaud=C3=A9?= , Stefan Hajnoczi , Richard Henderson , =?UTF-8?B?QWxleCBCZW5uw6ll?= , Thomas Huth , Paolo Bonzini , Kevin Wolf , Hanna Reitz , Christian Schoenebeck , Greg Kurz , Palmer Dabbelt , Alistair Francis , Weiwei Li , Daniel Henrique Barboza , Liu Zhiwei , =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= , =?UTF-8?Q?Daniel_P=2E_Berrang=C3=A9?= , Eduardo Habkost , Peter Maydell , qemu-block@nongnu.org, qemu-riscv@nongnu.org, qemu-arm@nongnu.org Content-Type: multipart/alternative; boundary="0000000000006acb94063281a09e" Received-SPF: pass client-ip=2a00:1450:4864:20::534; envelope-from=ktokunaga.mail@gmail.com; helo=mail-ed1-x534.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org --0000000000006acb94063281a09e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Pierrick, thank you for the feedback. > first, congrats for this work! > It would be really nice to have this available upstream, starting with a > modest TCI port, before having the tcg backend also. Sure, I'll split the patch series, starting with the TCI port. > Do you have recent information about wasm64? It seems to be something > that has been discussed for several years, without really seeing any > progress. According to the adoption status=E2=80=AF[1], wasm64 is supported by recent= versions of Chrome and Firefox. Emscripten also supports wasm64=E2=80=AF[2]. However= , it is not yet supported by Safari or libffi=E2=80=AF[3], and I haven't found a ro= admap for the adoption. [1] https://webassembly.org/features/ [2] https://emscripten.org/docs/tools_reference/settings_reference.html#memory6= 4 [3] https://github.com/libffi/libffi/blob/6a99edb8082f75e523e0d6ebaba42218b80e1= 0c8/README.md#supported-platforms > As Philippe said, we can't really revert that (it's now an assumption > for our softmmu implementation, and would break code if we enabled it > again now.) > > That said, we can always have a first version supporting only 32 bits > targets. And later, when wasm64 will be available, we can extend this to > all remaining ones. The main challenge I'm seeing is that I couldn't find a clear timeline for wasm64 adoption so it's difficult to predict when it will be widely available. Regarding the revert, the wasm backend supports 64-bit words, so the revert introduced in patch 06/10 is partial, as also pointed out by Paolo. --0000000000006acb94063281a09e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Pierrick, thank you for the feedback.<= /div>
> first, congrats for this work!
> It would be really nic= e to have this available upstream, starting with a
> modest TCI port,= before having the tcg backend also.

Sure, I'll split the patch = series, starting with the TCI port.

> Do you have recent informat= ion about wasm64? It seems to be something
> that has been discussed = for several years, without really seeing any
> progress.

Accor= ding to the adoption status=E2=80=AF[1], wasm64 is supported by recent vers= ions
of Chrome and Firefox. Emscripten also supports wasm64=E2=80=AF[2].= However, it is
not yet supported by Safari or libffi=E2=80=AF[3], and I= haven't found a roadmap for
the adoption.

[1] https://webassembly.org/features/
[2= ] https://emscripten.org/docs/tools_reference/settings_refere= nce.html#memory64
[3] = https://github.com/libffi/libffi/blob/6a99edb8082f75e523e0d6ebaba42218b80e1= 0c8/README.md#supported-platforms

> As Philippe said, we can&= #39;t really revert that (it's now an assumption
> for our softm= mu implementation, and would break code if we enabled it
> again now= .)
>
> That said, we can always have a first version supportin= g only 32 bits
> targets. And later, when wasm64 will be available, = we can extend this to
> all remaining ones.

The main challeng= e I'm seeing is that I couldn't find a clear timeline for
wasm64= adoption so it's difficult to predict when it will be widely
availa= ble.

Regarding the revert, the wasm backend supports 64-bit words, s= o the revert
introduced in patch 06/10 is partial, as also pointed out b= y Paolo.

--0000000000006acb94063281a09e--