qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Sunil Muthuswamy <sunilmut@microsoft.com>,
	Stefan Weil <sw@weilnetz.de>, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: 1879672@bugs.launchpad.net,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] WHPX: support for xcr0
Date: Wed, 20 May 2020 12:27:00 +0200	[thread overview]
Message-ID: <8a787221-0c91-3a65-1527-6d329466a6a1@redhat.com> (raw)
In-Reply-To: <MW2PR2101MB111666F06FADEC582CAE4184C0780@MW2PR2101MB1116.namprd21.prod.outlook.com>

+launchpad ticket

On 11/7/19 11:52 PM, Sunil Muthuswamy wrote:
>>> You will need the Windows 10 SDK for RS5 (build 17763) or above to
>>> to be able to compile this patch because of the definition of the
>>> XCR0 register.
>>>
>>> Changes since v1:
>>> - Added a sign-off line in the patch.
>>
>>
>> I am not very happy with the current situation which suggests using non
>> free header files from the Microsoft Windows SDK, thus making it
>> impossible to produce QEMU executables for Windows with WHPX support
>> without having legal complications.
>>
>> Could you please add the required headers with a suitable license to the
>> QEMU source code? That would clarify the license issue and make builds
>> with WHPX much easier because those files would not have to be extracted
>> from a very large SDK installation.
>>
>> It would also be acceptable if Microsoft could update the license
>> comments in those files and use a QEMU compatible license.
>>
> I agree in principle that there should be an easier way to consume the Windows
> SDK headers without having to play around with the licenses. I also agree that
> that will make life lot easier for many developers. I am reaching out
> internally here to see what can be done about this, but, that might take some
> time. Meanwhile, is it possible to make some progress on this patch?
> 
>> Kind regards
>> Stefan Weil
>>
>>
> 



WARNING: multiple messages have this Message-ID (diff)
From: "Philippe Mathieu-Daudé" <1879672@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1879672] Re: [PATCH v2] WHPX: support for xcr0
Date: Wed, 20 May 2020 10:27:00 -0000	[thread overview]
Message-ID: <8a787221-0c91-3a65-1527-6d329466a6a1@redhat.com> (raw)
Message-ID: <20200520102700.p-4Lvr84_ONWWGdC2EtheazwDZXe7d9Wsz83WfW6npM@z> (raw)
In-Reply-To: 158996968484.21371.12685815665992748631.malonedeb@wampee.canonical.com

+launchpad ticket

On 11/7/19 11:52 PM, Sunil Muthuswamy wrote:
>>> You will need the Windows 10 SDK for RS5 (build 17763) or above to
>>> to be able to compile this patch because of the definition of the
>>> XCR0 register.
>>>
>>> Changes since v1:
>>> - Added a sign-off line in the patch.
>>
>>
>> I am not very happy with the current situation which suggests using non
>> free header files from the Microsoft Windows SDK, thus making it
>> impossible to produce QEMU executables for Windows with WHPX support
>> without having legal complications.
>>
>> Could you please add the required headers with a suitable license to the
>> QEMU source code? That would clarify the license issue and make builds
>> with WHPX much easier because those files would not have to be extracted
>> from a very large SDK installation.
>>
>> It would also be acceptable if Microsoft could update the license
>> comments in those files and use a QEMU compatible license.
>>
> I agree in principle that there should be an easier way to consume the Windows
> SDK headers without having to play around with the licenses. I also agree that
> that will make life lot easier for many developers. I am reaching out
> internally here to see what can be done about this, but, that might take some
> time. Meanwhile, is it possible to make some progress on this patch?
> 
>> Kind regards
>> Stefan Weil
>>
>>
> 


** Tags added: windows

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1879672

Title:
  QEMU installer with WHPX support

Status in QEMU:
  New

Bug description:
  People often ask the community to add WHPX support to the QEMU installer for Windows,
  but it is impossible due to the license limitations of the WHPX SDK.

  The WinHvEmulation.h and WinHvPlatform.h header files needed are "All
  rights reserved".

  However these headers only contain struct definitions and integer constants,
  no functional code in macros or inline functions. See:
  https://www.mail-archive.com/qemu-devel@nongnu.org/msg645815.html
  It is questionable whether the headers alone can be considered copyrightable material.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1879672/+subscriptions


  reply	other threads:[~2020-05-20 10:28 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 19:48 [PATCH v2] WHPX: support for xcr0 Sunil Muthuswamy
2019-11-07 20:05 ` Stefan Weil
2019-11-07 22:52   ` Sunil Muthuswamy
2020-05-20 10:27     ` Philippe Mathieu-Daudé [this message]
2020-05-20 10:27       ` [Bug 1879672] " Philippe Mathieu-Daudé
2019-11-12 18:52 ` Sunil Muthuswamy
2019-11-13 14:56   ` Paolo Bonzini
2022-04-28  6:31 ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2020-05-20 10:14 [Bug 1879672] [NEW] QEMU installer with WHPX support Philippe Mathieu-Daudé
2020-05-20 10:25 ` [Bug 1879672] " Daniel Berrange
2020-05-20 12:30 ` Stefan Weil
2020-06-08  7:18 ` Philippe Mathieu-Daudé
2020-11-04 20:01 ` John Snow
2020-11-04 23:12   ` Philippe Mathieu-Daudé
2020-11-04 23:12     ` Philippe Mathieu-Daudé
2021-05-09 15:38 ` Philippe Mathieu-Daudé
2021-05-09 18:33 ` Stefan Weil
2021-05-27  7:45 ` Philippe Mathieu-Daudé
2020-02-18 20:38 [PATCH] WHPX: Assigning maintainer for Windows Hypervisor Platform Sunil Muthuswamy
2020-02-18 20:51 ` Justin Terry (SF)
2020-02-19  8:31   ` Philippe Mathieu-Daudé
2020-02-19 15:50     ` [EXTERNAL] " Justin Terry (SF)
2020-02-21  7:54       ` Stefan Weil
2020-02-24 19:43         ` Sunil Muthuswamy
2020-05-20 10:29           ` Philippe Mathieu-Daudé
2020-05-20 10:29             ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-05-19 21:59         ` Sunil Muthuswamy
2020-05-20 10:29           ` Philippe Mathieu-Daudé
2020-05-20 10:29             ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-02-21 17:15 ` Paolo Bonzini
2019-09-20 11:33 [PATCH v2 0/3] testing: Build WHPX enabled binaries Philippe Mathieu-Daudé
2019-09-20 11:33 ` [PATCH v2 1/3] target/i386: Fix broken build with WHPX enabled Philippe Mathieu-Daudé
2019-09-20 11:37   ` Paolo Bonzini
2019-09-20 11:33 ` [PATCH v2 2/3] tests/docker: Add fedora-win10sdk-cross image Philippe Mathieu-Daudé
2019-09-20 11:33 ` [PATCH v2 3/3] .shippable.yml: Build WHPX enabled binaries Philippe Mathieu-Daudé
2019-09-20 15:17 ` [PATCH v2 0/3] testing: " Philippe Mathieu-Daudé
2019-09-20 16:53   ` Justin Terry (VM)
2020-05-20 10:26     ` Philippe Mathieu-Daudé
2020-05-20 10:26       ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-07-31  8:33       ` Philippe Mathieu-Daudé
2020-07-31  8:33         ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-07-31 23:31         ` [EXTERNAL] " Sunil Muthuswamy
2020-08-03 10:51           ` Philippe Mathieu-Daudé
2020-08-03 10:51             ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-08-03 11:28             ` Stefan Weil
2020-08-03 20:25               ` Stefan Weil
2020-08-04  6:43                 ` Thomas Huth
2020-08-04  6:55                   ` Stefan Weil
2020-08-04  7:23                     ` Philippe Mathieu-Daudé
2020-08-04  7:23                       ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-08-04  7:42                       ` Stefan Weil
2020-08-04  7:52                         ` Philippe Mathieu-Daudé
2020-08-04  7:52                           ` [Bug 1879672] " Philippe Mathieu-Daudé
2020-08-04  8:10                         ` Thomas Huth
2020-08-04  9:23                           ` Daniel P. Berrangé
2020-08-04  9:23                             ` [Bug 1879672] " Daniel Berrange
2020-08-18 21:20                         ` [EXTERNAL] " Sunil Muthuswamy
2020-08-19  3:36                           ` Philippe Mathieu-Daudé
2020-08-19  3:36                             ` [Bug 1879672] " Philippe Mathieu-Daudé
2019-09-21  6:34 ` no-reply
2019-09-19 10:59 [Qemu-devel] [PATCH 0/2] " Philippe Mathieu-Daudé
2019-09-19 10:59 ` [Qemu-devel] [PATCH 1/2] tests/docker: Add fedora-win10sdk-cross image Philippe Mathieu-Daudé
2019-09-19 11:28   ` Alex Bennée
2019-09-19 11:35     ` Philippe Mathieu-Daudé
2019-09-19 10:59 ` [Qemu-devel] [PATCH 2/2] .shippable.yml: Build WHPX enabled binaries Philippe Mathieu-Daudé
2019-09-19 11:02   ` Philippe Mathieu-Daudé
2019-09-19 11:09 ` [Qemu-devel] [PATCH 0/2] testing: " Thomas Huth
2019-09-19 11:21   ` Philippe Mathieu-Daudé
2019-09-19 11:18 ` Stefan Weil
2019-09-19 11:26   ` Philippe Mathieu-Daudé
2020-05-20 10:25     ` Philippe Mathieu-Daudé
2020-05-20 10:25       ` [Bug 1879672] " Philippe Mathieu-Daudé
2019-09-19 11:41   ` [Qemu-devel] " Daniel P. Berrangé
2019-09-19 11:54     ` Philippe Mathieu-Daudé
2019-09-19 13:25       ` Daniel P. Berrangé

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=8a787221-0c91-3a65-1527-6d329466a6a1@redhat.com \
    --to=philmd@redhat.com \
    --cc=1879672@bugs.launchpad.net \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sunilmut@microsoft.com \
    --cc=sw@weilnetz.de \
    /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).