From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 02/11] evtchn: refactor low-level event channel port ops
Date: Mon, 16 Sep 2013 11:08:04 +0100 [thread overview]
Message-ID: <5236D884.2090803@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309151407330.5498@kaball.uk.xensource.com>
On 15/09/13 14:11, Stefano Stabellini wrote:
> On Sun, 15 Sep 2013, Stefano Stabellini wrote:
>> On Fri, 13 Sep 2013, David Vrabel wrote:
>>> diff --git a/xen/common/event_2l.c b/xen/common/event_2l.c
>>> new file mode 100644
>>> index 0000000..18c0c6e
>>> --- /dev/null
>>> +++ b/xen/common/event_2l.c
>>> @@ -0,0 +1,99 @@
>>> +/*
>>> + * Event channel port operations.
>>> + *
>>> + * Copyright (c) 2003-2006, K A Fraser.
>>> + *
>>> + * This source code is licensed under the GNU General Public License,
>>> + * Version 2 or later. See the file COPYING for more details.
>>> + */
>>
>> Does it have to be GPLv2 only? Can it be dual-licensed BSD to make it
>> easier for other operating systems to support the new interface?
>>
>
> I meant to quote the new Linux files:
>
> drivers/xen/events/events_internal.h
> drivers/xen/events/n-level.c
These will have to stay as GPLv2 as the are derived from the original
events.c which does not have any license stated (so we must assume GPLv2).
> drivers/xen/events/fifo.c
I will make this one dual GPLv2 or later and 2-clause BSD. Although, I
do think that any implementer would be better off basing their work off
the documentation rather a Linux-centric implementation.
David
next prev parent reply other threads:[~2013-09-16 10:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 16:56 [PATCHv3 0/11] Xen: FIFO-based event channel ABI David Vrabel
2013-09-13 16:56 ` [PATCH 01/11] debug: remove some event channel info from the 'i' and 'q' debug keys David Vrabel
2013-09-13 16:56 ` [PATCH 02/11] evtchn: refactor low-level event channel port ops David Vrabel
2013-09-15 13:06 ` Stefano Stabellini
2013-09-15 13:11 ` Stefano Stabellini
2013-09-16 10:08 ` David Vrabel [this message]
2013-09-15 13:20 ` Ian Campbell
2013-09-13 16:56 ` [PATCH 03/11] evtchn: print ABI specific state with the 'e' debug key David Vrabel
2013-09-13 16:56 ` [PATCH 04/11] evtchn: use a per-domain variable for the max number of event channels David Vrabel
2013-09-13 16:56 ` [PATCH 05/11] evtchn: dynamically allocate d->evtchn David Vrabel
2013-09-13 16:56 ` [PATCH 06/11] evtchn: alter internal object handling scheme David Vrabel
2013-09-13 16:56 ` [PATCH 07/11] evtchn: add FIFO-based event channel ABI David Vrabel
2013-09-16 6:59 ` Jan Beulich
2013-09-13 16:56 ` [PATCH 08/11] evtchn: implement EVTCHNOP_set_priority and add the set_priority hook David Vrabel
2013-09-13 16:56 ` [PATCH 09/11] evtchn: implement EVTCHNOP_set_limit David Vrabel
2013-09-13 18:32 ` Daniel De Graaf
2013-09-16 7:07 ` Jan Beulich
2013-09-16 10:00 ` David Vrabel
2013-09-16 10:33 ` Jan Beulich
2013-09-16 10:57 ` David Vrabel
2013-09-13 16:56 ` [PATCH 10/11] libxc: add xc_evtchn_set_limit() David Vrabel
2013-09-13 16:56 ` [PATCH 11/11] evtchn: add FIFO-based event channel hypercalls and port ops David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2013-09-27 10:55 [PATCHv4 0/11] Xen: FIFO-based event channel ABI David Vrabel
2013-09-27 10:55 ` [PATCH 02/11] evtchn: refactor low-level event channel port ops David Vrabel
2013-10-02 16:35 [PATCHv5 0/11] Xen: FIFO-based event channel ABI David Vrabel
2013-10-02 16:35 ` [PATCH 02/11] evtchn: refactor low-level event channel port ops David Vrabel
2013-10-08 12:40 [PATCHv6 00/11] Xen: FIFO-based event channel ABI David Vrabel
2013-10-08 12:40 ` [PATCH 02/11] evtchn: refactor low-level event channel port ops David Vrabel
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=5236D884.2090803@citrix.com \
--to=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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).