qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yu Ning <yu.ning@linux.intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>, Stefan Weil <sw@weilnetz.de>
Cc: 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: Fri, 17 Nov 2017 17:03:27 +0800	[thread overview]
Message-ID: <ed07d728-dc3d-3f45-23de-f4058aaf8f38@linux.intel.com> (raw)
In-Reply-To: <20171116180003.GO3111@localhost.localdomain>



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.
>
>>> Address this inconsistency by adding the BSD license to the QEMU
>>> file, per Stefan Weil's comment on this HAXM pull request:
>>>
>>>   https://github.com/intel/haxm/pull/2
> The existing code on qemu.git don't match the code on the GitHub
> repository above exactly, and its copyright history looks hard to
> track[1].

Right. I don't know when the QEMU header (hax-interface.h) first 
appeared, but I think it's probably a derivative of the HAXM ones, which 
date back to no later than June 2011.

> 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.

> Also, does it even make sense to keep the two licenses in the
> file?

I don't know the answer.  If it doesn't make sense, I can either remove 
the original GPLv2 license, or abandon this patch and later come back 
with another one implementing the above solution.

  reply	other threads:[~2017-11-17  9:03 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 [this message]
2017-11-19 21:31       ` Eduardo Habkost
2017-11-20  7:17         ` Yu Ning
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=ed07d728-dc3d-3f45-23de-f4058aaf8f38@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 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).