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 May, 2017

2 commits


03 May, 2017

1 commit


20 Jan, 2017

2 commits

  • Make ringtest work on s390 too.

    Signed-off-by: Halil Pasic
    Acked-by: Sascha Silbe
    Signed-off-by: Cornelia Huck

    Halil Pasic
     
  • Since ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work
    without /dev/cpu") run-on-all.sh uses seq 0 $HOST_AFFINITY as the list
    of ids of the CPUs to run the command on (assuming ids of online CPUs
    are consecutive and start from 0), where $HOST_AFFINITY is the highest
    CPU id in the system previously determined using lscpu. This can fail
    on systems with offline CPUs.

    Instead let's use lscpu to determine the list of online CPUs.

    Signed-off-by: Halil Pasic
    Fixes: ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work without
    /dev/cpu")
    Reviewed-by: Sascha Silbe
    Signed-off-by: Cornelia Huck

    Halil Pasic
     

31 Oct, 2016

3 commits


15 Aug, 2016

1 commit

  • Recent changes to ptr_ring broke the ringtest
    which lacks a likely() stub. Fix it up.

    Fixes: 982fb490c298896d15e9323a882f34a57c11ff56
    ("ptr_ring: support zero length ring")
    Signed-off-by: Michael S. Tsirkin

    Michael S. Tsirkin
     

01 Jul, 2016

1 commit


30 Jun, 2016

1 commit


16 Jun, 2016

1 commit


06 Jun, 2016

3 commits


23 May, 2016

2 commits


26 Jan, 2016

1 commit

  • This adds micro-benchmarks useful for tuning virtio ring layouts.
    Three layouts are currently implemented:

    - virtio 0.9 compatible one
    - an experimental extension bypassing the ring index, polling ring
    itself instead
    - an experimental extension bypassing avail and used ring completely

    Typical use:

    sh run-on-all.sh perf stat -r 10 --log-fd 1 -- ./ring

    It doesn't depend on the kernel directly, but it's handy
    to have as much virtio stuff as possible in one tree.

    Signed-off-by: Michael S. Tsirkin

    Michael S. Tsirkin