qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/3] WHPX introduce changes for Windows Insider


From: Frank Yang
Subject: Re: [Qemu-devel] [PATCH 0/3] WHPX introduce changes for Windows Insider SDK 17110
Date: Thu, 24 Jan 2019 08:56:33 -0800

Is this useful at all for the Android Emulator? Does it break backward
compatibility for older Windows versions?

On Thu, Jan 17, 2019 at 12:39 PM Stefan Weil <address@hidden> wrote:

> Am 14.03.2018 um 15:52 schrieb Justin Terry (VM) via Qemu-devel:
> > This change set fixes two breaking changes that were introduced in the
> > Windows Insider SDK 17110. First, a change to the WHvGetCapability
> function
> > decl to include the 'out' WrittenSizeInBytes. Second, changes to the
> > WHvSetPartitionProperty function decl and WHV_PARTITION_PROPERTY
> structure
> > to directly pass the PropertyCode at invocation.
> >
> > Lastly, it introduces a major performance improvement in
> whpx_vcpu_post_run
> > using the VpContext exit structure rather than another round trip call to
> > WHvGetVirtualProcessorRegisters to synchronize vp state.
> >
> > QEMU compiled against this SDK (17110+) is expected to work on all
> Windows
> > Insider Builds (17115+).
> >
> > Thanks,
> > Justin Terry
>
>
> Hi Justin,
>
> as far as I know it still not possible to cross build a legal QEMU for
> Windows on a Linux machine due to the license limitations of the SDK
> which is needed. The header files needed for the QEMU build are "All
> rights reserved".
>
> People often ask me to add WHPX support to the QEMU installer for
> Windows, but I have to tell them that I cannot do that currently.
>
> This problem could be solved if the necessary header files were added to
> QEMU with a permissive license by someone who has the rights to do so.
>
> Could you add WinHvEmulation.h and WinHvPlatform.h or am I allowed to
> make such files from the documentation at https://docs.microsoft.com/?
>
> Thanks,
> Stefan Weil
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]