From: Yu Ning <yu.ning@linux.intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Yu Ning <yu.ning@intel.com>, Richard Henderson <rth@twiddle.net>,
Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] [PATCH] hax-interface: Add BSD license
Date: Mon, 20 Nov 2017 15:17:34 +0800 [thread overview]
Message-ID: <1516fc97-6b46-5a3b-3226-d89b55974cea@linux.intel.com> (raw)
In-Reply-To: <20171119213130.GI3037@localhost.localdomain>
On 11/20/2017 5:31, Eduardo Habkost wrote:
> On Fri, Nov 17, 2017 at 05:03:27PM +0800, Yu Ning wrote:
>> On 11/17/2017 2:00, Eduardo Habkost wrote:
>>> On Thu, Nov 16, 2017 at 07:47:44AM +0100, Stefan Weil wrote:
>>>> Am 16.11.2017 um 07:50 schrieb yu.ning@linux.intel.com:
>>>>> From: Yu Ning <yu.ning@intel.com>
>>>>>
>>>>> hax-interface.h defines the interface between the HAXM kernel
>>>>> module and the HAXM QEMU accelerator. The same code can be found in
>>>>> the following files of the HAXM kernel module:
>>>>>
>>>>> include/hax_interface.h
>>>>> include/vcpu_state.h
>>>>> core/include/vm.h
>>>>>
>>>>> These files are now open source under the 3-clause BSD license,
>>>>> whereas hax-interface.h in QEMU uses GPLv2.
>>> Why is this a problem?
>> I know very little about licenses. If this is not a problem, I'm happy to
>> just abandon this patch.
> As far as I can see, this is not a problem for the QEMU project
> at all, as QEMU as a whole is GPLv2.
>
> It would make sense to update the license if we wanted to keep
> our header file in sync with some other source tree (e.g. the one
> from Intel), but this doesn't seem to be the case here (yet?).
>
I see, that makes sense.
>
>>
>>> If we really care about consistency between the two
>>> projects, shouldn't we just delete the existing file and copy the
>>> headers from github.com/intel/haxm directly?
>> That's a good solution, but not feasible at the moment, because in the HAXM
>> kernel module, a small piece of the interface code currently resides in an
>> internal header (core/include/vm.h). Probably we should clean up the
>> interface headers on the HAXM side, and then push the change to QEMU.
> This would be nice, so we wouldn't need to maintain a different
> header file in QEMU. Should we open an issue at
> https://github.com/intel/haxm?
>
Here: https://github.com/intel/haxm/issues/9
The API headers in the HAXM tree depend on another header, i.e. either
hax_types_windows.h or hax_types_mac.h, which defines some basic data
types (uint64_t, etc.) and macros (PACKED, ALIGNED, etc.). If we want
to use the same files for QEMU, we'll need to figure out an elegant way
to provide those definitions. Any suggestions?
next prev parent reply other threads:[~2017-11-20 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 6:50 [Qemu-devel] [PATCH] hax-interface: Add BSD license yu.ning
2017-11-16 6:47 ` Stefan Weil
2017-11-16 18:00 ` Eduardo Habkost
2017-11-17 9:03 ` Yu Ning
2017-11-19 21:31 ` Eduardo Habkost
2017-11-20 7:17 ` Yu Ning [this message]
2017-11-20 7:41 ` Kamil Rytarowski
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=1516fc97-6b46-5a3b-3226-d89b55974cea@linux.intel.com \
--to=yu.ning@linux.intel.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.de \
--cc=vpalatin@chromium.org \
--cc=yu.ning@intel.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.