License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 08:07:57 -06:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2007-07-17 19:37:05 -06:00
|
|
|
#ifndef _XEN_EVENTS_H
|
|
|
|
#define _XEN_EVENTS_H
|
|
|
|
|
2007-07-17 19:37:06 -06:00
|
|
|
#include <linux/interrupt.h>
|
2019-06-21 12:47:03 -06:00
|
|
|
#include <linux/irq.h>
|
2014-02-27 11:15:35 -07:00
|
|
|
#ifdef CONFIG_PCI_MSI
|
|
|
|
#include <linux/msi.h>
|
|
|
|
#endif
|
2007-07-17 19:37:06 -06:00
|
|
|
|
|
|
|
#include <xen/interface/event_channel.h>
|
|
|
|
#include <asm/xen/hypercall.h>
|
2008-04-02 11:53:56 -06:00
|
|
|
#include <asm/xen/events.h>
|
2007-07-17 19:37:05 -06:00
|
|
|
|
2013-09-23 14:03:38 -06:00
|
|
|
unsigned xen_evtchn_nr_channels(void);
|
|
|
|
|
2007-07-17 19:37:06 -06:00
|
|
|
int bind_evtchn_to_irq(unsigned int evtchn);
|
2007-07-17 19:37:05 -06:00
|
|
|
int bind_evtchn_to_irqhandler(unsigned int evtchn,
|
2007-07-17 19:37:06 -06:00
|
|
|
irq_handler_t handler,
|
2007-07-17 19:37:05 -06:00
|
|
|
unsigned long irqflags, const char *devname,
|
|
|
|
void *dev_id);
|
2015-05-19 11:40:49 -06:00
|
|
|
int bind_virq_to_irq(unsigned int virq, unsigned int cpu, bool percpu);
|
2007-07-17 19:37:05 -06:00
|
|
|
int bind_virq_to_irqhandler(unsigned int virq, unsigned int cpu,
|
2007-07-17 19:37:06 -06:00
|
|
|
irq_handler_t handler,
|
|
|
|
unsigned long irqflags, const char *devname,
|
|
|
|
void *dev_id);
|
|
|
|
int bind_ipi_to_irqhandler(enum ipi_vector ipi,
|
|
|
|
unsigned int cpu,
|
|
|
|
irq_handler_t handler,
|
|
|
|
unsigned long irqflags,
|
|
|
|
const char *devname,
|
|
|
|
void *dev_id);
|
2014-08-27 22:44:09 -06:00
|
|
|
int bind_interdomain_evtchn_to_irq(unsigned int remote_domain,
|
|
|
|
unsigned int remote_port);
|
2009-02-09 13:05:50 -07:00
|
|
|
int bind_interdomain_evtchn_to_irqhandler(unsigned int remote_domain,
|
|
|
|
unsigned int remote_port,
|
|
|
|
irq_handler_t handler,
|
|
|
|
unsigned long irqflags,
|
|
|
|
const char *devname,
|
|
|
|
void *dev_id);
|
2007-07-17 19:37:05 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Common unbind function for all event sources. Takes IRQ to unbind from.
|
|
|
|
* Automatically closes the underlying event channel (even for bindings
|
|
|
|
* made with bind_evtchn_to_irqhandler()).
|
|
|
|
*/
|
|
|
|
void unbind_from_irqhandler(unsigned int irq, void *dev_id);
|
|
|
|
|
2013-09-23 05:47:26 -06:00
|
|
|
#define XEN_IRQ_PRIORITY_MAX EVTCHN_FIFO_PRIORITY_MAX
|
|
|
|
#define XEN_IRQ_PRIORITY_DEFAULT EVTCHN_FIFO_PRIORITY_DEFAULT
|
|
|
|
#define XEN_IRQ_PRIORITY_MIN EVTCHN_FIFO_PRIORITY_MIN
|
|
|
|
int xen_set_irq_priority(unsigned irq, unsigned priority);
|
|
|
|
|
2011-10-27 15:58:47 -06:00
|
|
|
/*
|
|
|
|
* Allow extra references to event channels exposed to userspace by evtchn
|
|
|
|
*/
|
|
|
|
int evtchn_make_refcounted(unsigned int evtchn);
|
|
|
|
int evtchn_get(unsigned int evtchn);
|
|
|
|
void evtchn_put(unsigned int evtchn);
|
|
|
|
|
2007-07-17 19:37:06 -06:00
|
|
|
void xen_send_IPI_one(unsigned int cpu, enum ipi_vector vector);
|
2008-05-26 16:31:23 -06:00
|
|
|
void rebind_evtchn_irq(int evtchn, int irq);
|
2019-06-21 12:47:03 -06:00
|
|
|
int xen_set_affinity_evtchn(struct irq_desc *desc, unsigned int tcpu);
|
2007-07-17 19:37:06 -06:00
|
|
|
|
2007-07-17 19:37:05 -06:00
|
|
|
static inline void notify_remote_via_evtchn(int port)
|
|
|
|
{
|
|
|
|
struct evtchn_send send = { .port = port };
|
|
|
|
(void)HYPERVISOR_event_channel_op(EVTCHNOP_send, &send);
|
|
|
|
}
|
|
|
|
|
2011-03-10 09:08:05 -07:00
|
|
|
void notify_remote_via_irq(int irq);
|
2008-05-26 16:31:27 -06:00
|
|
|
|
2011-03-10 09:08:05 -07:00
|
|
|
void xen_irq_resume(void);
|
2008-05-26 16:31:27 -06:00
|
|
|
|
xen: implement Xen-specific spinlocks
The standard ticket spinlocks are very expensive in a virtual
environment, because their performance depends on Xen's scheduler
giving vcpus time in the order that they're supposed to take the
spinlock.
This implements a Xen-specific spinlock, which should be much more
efficient.
The fast-path is essentially the old Linux-x86 locks, using a single
lock byte. The locker decrements the byte; if the result is 0, then
they have the lock. If the lock is negative, then locker must spin
until the lock is positive again.
When there's contention, the locker spin for 2^16[*] iterations waiting
to get the lock. If it fails to get the lock in that time, it adds
itself to the contention count in the lock and blocks on a per-cpu
event channel.
When unlocking the spinlock, the locker looks to see if there's anyone
blocked waiting for the lock by checking for a non-zero waiter count.
If there's a waiter, it traverses the per-cpu "lock_spinners"
variable, which contains which lock each CPU is waiting on. It picks
one CPU waiting on the lock and sends it an event to wake it up.
This allows efficient fast-path spinlock operation, while allowing
spinning vcpus to give up their processor time while waiting for a
contended lock.
[*] 2^16 iterations is threshold at which 98% locks have been taken
according to Thomas Friebel's Xen Summit talk "Preventing Guests from
Spinning Around". Therefore, we'd expect the lock and unlock slow
paths will only be entered 2% of the time.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Christoph Lameter <clameter@linux-foundation.org>
Cc: Petr Tesarik <ptesarik@suse.cz>
Cc: Virtualization <virtualization@lists.linux-foundation.org>
Cc: Xen devel <xen-devel@lists.xensource.com>
Cc: Thomas Friebel <thomas.friebel@amd.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-07 13:07:53 -06:00
|
|
|
/* Clear an irq's pending state, in preparation for polling on it */
|
|
|
|
void xen_clear_irq_pending(int irq);
|
2008-08-20 18:02:18 -06:00
|
|
|
void xen_set_irq_pending(int irq);
|
|
|
|
bool xen_test_irq_pending(int irq);
|
xen: implement Xen-specific spinlocks
The standard ticket spinlocks are very expensive in a virtual
environment, because their performance depends on Xen's scheduler
giving vcpus time in the order that they're supposed to take the
spinlock.
This implements a Xen-specific spinlock, which should be much more
efficient.
The fast-path is essentially the old Linux-x86 locks, using a single
lock byte. The locker decrements the byte; if the result is 0, then
they have the lock. If the lock is negative, then locker must spin
until the lock is positive again.
When there's contention, the locker spin for 2^16[*] iterations waiting
to get the lock. If it fails to get the lock in that time, it adds
itself to the contention count in the lock and blocks on a per-cpu
event channel.
When unlocking the spinlock, the locker looks to see if there's anyone
blocked waiting for the lock by checking for a non-zero waiter count.
If there's a waiter, it traverses the per-cpu "lock_spinners"
variable, which contains which lock each CPU is waiting on. It picks
one CPU waiting on the lock and sends it an event to wake it up.
This allows efficient fast-path spinlock operation, while allowing
spinning vcpus to give up their processor time while waiting for a
contended lock.
[*] 2^16 iterations is threshold at which 98% locks have been taken
according to Thomas Friebel's Xen Summit talk "Preventing Guests from
Spinning Around". Therefore, we'd expect the lock and unlock slow
paths will only be entered 2% of the time.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Christoph Lameter <clameter@linux-foundation.org>
Cc: Petr Tesarik <ptesarik@suse.cz>
Cc: Virtualization <virtualization@lists.linux-foundation.org>
Cc: Xen devel <xen-devel@lists.xensource.com>
Cc: Thomas Friebel <thomas.friebel@amd.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-07 13:07:53 -06:00
|
|
|
|
|
|
|
/* Poll waiting for an irq to become pending. In the usual case, the
|
|
|
|
irq will be disabled so it won't deliver an interrupt. */
|
|
|
|
void xen_poll_irq(int irq);
|
|
|
|
|
2009-11-05 14:33:09 -07:00
|
|
|
/* Poll waiting for an irq to become pending with a timeout. In the usual case,
|
|
|
|
* the irq will be disabled so it won't deliver an interrupt. */
|
|
|
|
void xen_poll_irq_timeout(int irq, u64 timeout);
|
|
|
|
|
2009-02-06 20:20:31 -07:00
|
|
|
/* Determine the IRQ which is bound to an event channel */
|
|
|
|
unsigned irq_from_evtchn(unsigned int evtchn);
|
2013-03-13 09:29:25 -06:00
|
|
|
int irq_from_virq(unsigned int cpu, unsigned int virq);
|
|
|
|
unsigned int evtchn_from_irq(unsigned irq);
|
2009-02-06 20:20:31 -07:00
|
|
|
|
2018-08-28 01:40:12 -06:00
|
|
|
#ifdef CONFIG_XEN_PVHVM
|
2010-05-14 05:40:51 -06:00
|
|
|
/* Xen HVM evtchn vector callback */
|
2011-03-10 09:08:05 -07:00
|
|
|
void xen_hvm_callback_vector(void);
|
x86, trace: Add irq vector tracepoints
[Purpose of this patch]
As Vaibhav explained in the thread below, tracepoints for irq vectors
are useful.
http://www.spinics.net/lists/mm-commits/msg85707.html
<snip>
The current interrupt traces from irq_handler_entry and irq_handler_exit
provide when an interrupt is handled. They provide good data about when
the system has switched to kernel space and how it affects the currently
running processes.
There are some IRQ vectors which trigger the system into kernel space,
which are not handled in generic IRQ handlers. Tracing such events gives
us the information about IRQ interaction with other system events.
The trace also tells where the system is spending its time. We want to
know which cores are handling interrupts and how they are affecting other
processes in the system. Also, the trace provides information about when
the cores are idle and which interrupts are changing that state.
<snip>
On the other hand, my usecase is tracing just local timer event and
getting a value of instruction pointer.
I suggested to add an argument local timer event to get instruction pointer before.
But there is another way to get it with external module like systemtap.
So, I don't need to add any argument to irq vector tracepoints now.
[Patch Description]
Vaibhav's patch shared a trace point ,irq_vector_entry/irq_vector_exit, in all events.
But there is an above use case to trace specific irq_vector rather than tracing all events.
In this case, we are concerned about overhead due to unwanted events.
So, add following tracepoints instead of introducing irq_vector_entry/exit.
so that we can enable them independently.
- local_timer_vector
- reschedule_vector
- call_function_vector
- call_function_single_vector
- irq_work_entry_vector
- error_apic_vector
- thermal_apic_vector
- threshold_apic_vector
- spurious_apic_vector
- x86_platform_ipi_vector
Also, introduce a logic switching IDT at enabling/disabling time so that a time penalty
makes a zero when tracepoints are disabled. Detailed explanations are as follows.
- Create trace irq handlers with entering_irq()/exiting_irq().
- Create a new IDT, trace_idt_table, at boot time by adding a logic to
_set_gate(). It is just a copy of original idt table.
- Register the new handlers for tracpoints to the new IDT by introducing
macros to alloc_intr_gate() called at registering time of irq_vector handlers.
- Add checking, whether irq vector tracing is on/off, into load_current_idt().
This has to be done below debug checking for these reasons.
- Switching to debug IDT may be kicked while tracing is enabled.
- On the other hands, switching to trace IDT is kicked only when debugging
is disabled.
In addition, the new IDT is created only when CONFIG_TRACING is enabled to avoid being
used for other purposes.
Signed-off-by: Seiji Aguchi <seiji.aguchi@hds.com>
Link: http://lkml.kernel.org/r/51C323ED.5050708@hds.com
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
2013-06-20 09:46:53 -06:00
|
|
|
#ifdef CONFIG_TRACING
|
|
|
|
#define trace_xen_hvm_callback_vector xen_hvm_callback_vector
|
|
|
|
#endif
|
2018-08-28 01:40:12 -06:00
|
|
|
#endif
|
2010-05-14 05:40:51 -06:00
|
|
|
int xen_set_callback_via(uint64_t via);
|
|
|
|
void xen_evtchn_do_upcall(struct pt_regs *regs);
|
|
|
|
void xen_hvm_evtchn_do_upcall(void);
|
|
|
|
|
2011-03-10 09:08:07 -07:00
|
|
|
/* Bind a pirq for a physical interrupt to an irq. */
|
|
|
|
int xen_bind_pirq_gsi_to_irq(unsigned gsi,
|
|
|
|
unsigned pirq, int shareable, char *name);
|
2010-10-11 08:30:09 -06:00
|
|
|
|
|
|
|
#ifdef CONFIG_PCI_MSI
|
2011-03-10 09:08:07 -07:00
|
|
|
/* Allocate a pirq for a MSI style physical interrupt. */
|
2011-02-18 09:43:32 -07:00
|
|
|
int xen_allocate_pirq_msi(struct pci_dev *dev, struct msi_desc *msidesc);
|
2011-03-10 09:08:07 -07:00
|
|
|
/* Bind an PSI pirq to an irq. */
|
2011-02-18 09:43:32 -07:00
|
|
|
int xen_bind_pirq_msi_to_irq(struct pci_dev *dev, struct msi_desc *msidesc,
|
2014-02-27 11:15:35 -07:00
|
|
|
int pirq, int nvec, const char *name, domid_t domid);
|
2010-10-11 08:30:09 -06:00
|
|
|
#endif
|
2010-10-01 10:20:09 -06:00
|
|
|
|
2010-03-18 14:31:34 -06:00
|
|
|
/* De-allocates the above mentioned physical interrupt. */
|
|
|
|
int xen_destroy_irq(int irq);
|
|
|
|
|
2010-12-01 07:51:44 -07:00
|
|
|
/* Return irq from pirq */
|
|
|
|
int xen_irq_from_pirq(unsigned pirq);
|
|
|
|
|
2011-02-24 12:20:12 -07:00
|
|
|
/* Return the pirq allocated to the irq. */
|
|
|
|
int xen_pirq_from_irq(unsigned irq);
|
|
|
|
|
2012-05-21 09:54:10 -06:00
|
|
|
/* Return the irq allocated to the gsi */
|
|
|
|
int xen_irq_from_gsi(unsigned gsi);
|
|
|
|
|
2010-11-08 12:26:36 -07:00
|
|
|
/* Determine whether to ignore this IRQ if it is passed to a guest. */
|
|
|
|
int xen_test_irq_shared(int irq);
|
|
|
|
|
2012-09-14 07:37:32 -06:00
|
|
|
/* initialize Xen IRQ subsystem */
|
|
|
|
void xen_init_IRQ(void);
|
2007-07-17 19:37:05 -06:00
|
|
|
#endif /* _XEN_EVENTS_H */
|