From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Haitao Shan <hshan@google.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/6] Adding the Android Emulator hypervisor driver accelerator
Date: Fri, 3 Mar 2023 10:33:54 +0000 [thread overview]
Message-ID: <ZAHNEtV0N+9JyZTk@redhat.com> (raw)
In-Reply-To: <CAGD3tSzW1QoAsn+uGjoAkBegLt1iZ=9YWDFcvqbcHMr0S_5kVw@mail.gmail.com>
On Thu, Mar 02, 2023 at 06:25:59PM -0800, Haitao Shan wrote:
> The Android Emulator hypervisor driver is a hypervisor for Windows (7
> or later), made by porting the KVM from the linux kernel 4.9-rc7. Its
> initial purpose was to support the Android Emulator on the AMD
> platforms as the old name "Android Emulator Hypervisor Driver for AMD
> Processors" suggested. Despite the name, Intel processors have been
> supported ever since its first release. Since Intel dropped HAXM support,
> the android emulator is switching from HAXM to AEHD.
When HAXM was proposed for deprecation & removal from QEMU, the suggestion
was that users should switch to Windows' native replacement WHPX, which
QEMU already has support for.
What is the rationale for wanting to introduce a 3rd party hypervisor
solution like AEHD, for the Android emulator, rather than just sticking
with the standard WHPX hypervisor available for Windows ? IIUC, the
Android emulator can already support WHPX according to these pages:
https://developer.android.com/studio/run/emulator-acceleration
https://learn.microsoft.com/en-us/dotnet/maui/android/emulator/hardware-acceleration?view=net-maui-7.0
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-03 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 2:25 [PATCH 0/6] Adding the Android Emulator hypervisor driver accelerator Haitao Shan
2023-03-03 10:33 ` Daniel P. Berrangé [this message]
2023-03-03 16:50 ` Haitao Shan
2023-03-03 17:12 ` Daniel P. Berrangé
2023-03-03 17:39 ` Haitao Shan
2023-04-04 11:55 ` Paolo Bonzini
2023-04-18 16:54 ` Haitao Shan
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 9:08 startergo via
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=ZAHNEtV0N+9JyZTk@redhat.com \
--to=berrange@redhat.com \
--cc=hshan@google.com \
--cc=qemu-devel@nongnu.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).