02 Nov, 2017

1 commit

  • 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
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

09 Mar, 2016

1 commit

  • echo nop > /sys/kernel/debug/tracing/options/current_tracer
    echo 1 > /sys/kernel/debug/tracing/options/test_nop_accept
    echo 0 > /sys/kernel/debug/tracing/options/test_nop_accept
    echo 1 > /sys/kernel/debug/tracing/options/test_nop_refuse

    Before the fix, the dmesg is a bit ugly since a align issue.

    [ 191.973081] nop_test_accept flag set to 1: we accept. Now cat trace_options to see the result
    [ 195.156942] nop_test_refuse flag set to 1: we refuse.Now cat trace_options to see the result

    After the fix, the dmesg will show aligned log for nop_test_refuse and nop_test_accept.

    [ 2718.032413] nop_test_refuse flag set to 1: we refuse. Now cat trace_options to see the result
    [ 2734.253360] nop_test_accept flag set to 1: we accept. Now cat trace_options to see the result

    Link: http://lkml.kernel.org/r/1457444222-8654-2-git-send-email-chuhu@redhat.com

    Signed-off-by: Chunyu Hu
    Signed-off-by: Steven Rostedt

    Chunyu Hu
     

23 Jan, 2015

1 commit


30 Apr, 2014

1 commit

  • Now that the ring buffer has a built in way to wake up readers
    when there's data, using irq_work such that it is safe to do it
    in any context. But it was still using the old "poor man's"
    wait polling that checks every 1/10 of a second to see if it
    should wake up a waiter. This makes the latency for a wake up
    excruciatingly long. No need to do that anymore.

    Completely remove the different wait_poll types from the tracers
    and have them all use the default one now.

    Reported-by: Johannes Berg
    Signed-off-by: Steven Rostedt

    Steven Rostedt (Red Hat)
     

21 Feb, 2014

2 commits


23 Mar, 2009

1 commit

  • Impact: display events when they arrive

    Now that the events don't use wake_up() anymore, we need the nop
    tracer to poll waiting for events on the pipe. Especially because
    nop is useful to look at orphan traces types (traces types that
    don't rely on specific tracers) because it doesn't produce traces
    itself.

    And unlike other tracers that trigger specific traces periodically,
    nop triggers no traces by itself that can wake him.

    Signed-off-by: Frederic Weisbecker
    Cc: Steven Rostedt
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     

06 Feb, 2009

1 commit


29 Jan, 2009

1 commit


18 Nov, 2008

1 commit

  • Impact: give an example on how to use specific tracer flags

    This patch propose to use the nop tracer to provide an
    example for using the tracer's custom flags implementation.

    V2: replace structures and defines just after the headers includes for
    cleanliness.
    V3: replace defines by enum values.

    Signed-off-by: Frederic Weisbecker
    Acked-by: Steven Noonan
    Acked-by: Steven Rostedt
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     

16 Nov, 2008

1 commit

  • Impact: extend the ->init() method with the ability to fail

    This bring a way to know if the initialization of a tracer successed.
    A tracer must return 0 on success and a traditional error (ie:
    -ENOMEM) if it fails.

    If a tracer fails to init, it is free to print a detailed warn. The
    tracing api will not and switch to a new tracer will just return the
    error from the init callback.

    Note: this will be used for the return tracer.

    Signed-off-by: Frederic Weisbecker
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     

08 Nov, 2008

2 commits


14 Oct, 2008

4 commits