qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [RFC PATCH] docs: Add roadmap for heterogeneous emulation
Date: Thu, 21 Nov 2024 07:18:38 +0100	[thread overview]
Message-ID: <429ae2fe-9fe7-4c45-a627-70415b3d727b@redhat.com> (raw)
In-Reply-To: <20241119161312.41346-1-philmd@linaro.org>

On 19/11/2024 17.13, Philippe Mathieu-Daudé wrote:
> This document tries to document the steps required to:
> 
>   - Have a single binary to run system emulations
>   - Emulate different architectures in the same process
>   - Have QEMU assemble dynamic machines at runtime
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> This is the document that was discussed at the KVM forum 2024 BoF.
> Since then I did some changes but I figured it'd be better to
> post the discussed doc first then comment the changes on the list.
> ---
>   docs/devel/heterogeneous-emulation-roadmap.md | 892 ++++++++++++++++++

Meta-question: So far we tracked feature planning in the wiki 
(https://wiki.qemu.org/Features) ... do we want to change that now? 
Otherwise, this content should maybe be rather put into the wiki instead?

  Thomas



  reply	other threads:[~2024-11-21  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 16:13 [RFC PATCH] docs: Add roadmap for heterogeneous emulation Philippe Mathieu-Daudé
2024-11-21  6:18 ` Thomas Huth [this message]
2024-11-21  8:55   ` Alex Bennée

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=429ae2fe-9fe7-4c45-a627-70415b3d727b@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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).