From: "Alex Bennée" <alex.bennee@linaro.org>
To: RR NN <rnn59437@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Support Android hypervisors
Date: Thu, 22 Feb 2024 10:39:35 +0000 [thread overview]
Message-ID: <877ciwail4.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAK4oD7DS0WiZcze37b8ERh50_ht=HNS3Bk8aeRmCjx_ndMG1gw@mail.gmail.com> (RR NN's message of "Thu, 22 Feb 2024 09:07:54 +0330")
RR NN <rnn59437@gmail.com> writes:
> Android Virtualization Framework (AVF) supports "KVM(pKVM)"
Does the user-space API change for pKVM? As far as I'm aware the
userspace API is the same.
> also Qualcomm's "Gunyah"
Feel free to review:
https://patchew.org/QEMU/20240109090039.1636383-1-quic._5Fsvaddagi@quicinc.com/
> and MediaTek's "GenieZone" as
> the hypervisor. Please Add these hypervisors to QEMU.
Generally the QEMU community hasn't the bandwidth to implement every
requested feature so we rely on those with an interest to step forward
and work on the code.
That said it doesn't look like the kernel side of UAPI is anywhere close
to getting merged:
https://lore.kernel.org/lkml/20240129083302.26044-1-yi-de.wu@mediatek.com/
I should also note that proprietary hypervisors locked to specific SoC's
make it even more challenging for open source developers to work on it.
I for one wouldn't want to try and get a hypervisor working if I
couldn't see the code and get it up and running under QEMU's emulation.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-02-22 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 5:37 Support Android hypervisors RR NN
2024-02-22 6:00 ` Trilok Soni
2024-02-22 10:39 ` Alex Bennée [this message]
2024-02-24 6:27 ` RR NN
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 16:00 RR NN
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=877ciwail4.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rnn59437@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.