<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/tools/bpf/bpftool/Documentation, branch linux-4.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2017-11-30T01:09:29Z</updated>
<entry>
<title>tools: bpftool: unify installation directories</title>
<updated>2017-11-30T01:09:29Z</updated>
<author>
<name>Quentin Monnet</name>
</author>
<published>2017-11-29T01:44:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=507e590da398a0e3438d563b5e736c3f2a7749d7'/>
<id>urn:sha1:507e590da398a0e3438d563b5e736c3f2a7749d7</id>
<content type='text'>
Programs and documentation not managed by package manager are generally
installed under /usr/local/, instead of the user's home directory. In
particular, `man` is generally able to find manual pages under
`/usr/local/share/man`.

bpftool generally follows perf's example, and perf installs to home
directory. However bpftool requires root credentials, so it seems
sensible to follow the more common convention of installing files under
/usr/local instead. So, make /usr/local the default prefix for
installing the binary with `make install`, and the documentation with
`make doc-install`. Also, create /usr/local/sbin if it does not exist.

Note that the bash-completion file, however, is still installed under
/usr/share/bash-completion/completions, as the default setup for bash
does not attempt to load completion files under /usr/local/.

Reported-by: David Beckett &lt;david.beckett@netronome.com&gt;
Signed-off-by: Quentin Monnet &lt;quentin.monnet@netronome.com&gt;
Acked-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Signed-off-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: optionally show filenames of pinned objects</title>
<updated>2017-11-11T03:35:41Z</updated>
<author>
<name>Prashant Bhole</name>
</author>
<published>2017-11-08T04:55:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c541b73466549c4aa4ee20ccd04ba52e4c95d6eb'/>
<id>urn:sha1:c541b73466549c4aa4ee20ccd04ba52e4c95d6eb</id>
<content type='text'>
Making it optional to show file names of pinned objects because
it scans complete bpf-fs filesystem which is costly.
Added option -f|--bpffs. Documentation updated.

Signed-off-by: Prashant Bhole &lt;bhole_prashant_q7@lab.ntt.co.jp&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: update documentation for --json and --pretty usage</title>
<updated>2017-10-24T00:25:09Z</updated>
<author>
<name>Quentin Monnet</name>
</author>
<published>2017-10-23T16:24:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0641c3c890d480abeb237b92a5ee4b99a22319c6'/>
<id>urn:sha1:0641c3c890d480abeb237b92a5ee4b99a22319c6</id>
<content type='text'>
Update the documentation to provide help about JSON output generation,
and add an example in bpftool-prog manual page.

Also reintroduce an example that was left aside when the tool was moved
from GitHub to the kernel sources, in order to show how to mount the
bpffs file system (to pin programs) inside the bpftool-prog manual page.

Signed-off-by: Quentin Monnet &lt;quentin.monnet@netronome.com&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: add cosmetic changes for the manual pages</title>
<updated>2017-10-24T00:25:09Z</updated>
<author>
<name>Quentin Monnet</name>
</author>
<published>2017-10-23T16:24:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=47ff7ac6d706c6f08153294c87287aeec183b211'/>
<id>urn:sha1:47ff7ac6d706c6f08153294c87287aeec183b211</id>
<content type='text'>
Make the look-and-feel of the manual pages somewhat closer to other
manual pages, such as the ones from the utilities from iproute2, by
highlighting more keywords.

Signed-off-by: Quentin Monnet &lt;quentin.monnet@netronome.com&gt;
Acked-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: add option parsing to bpftool, --help and --version</title>
<updated>2017-10-24T00:25:08Z</updated>
<author>
<name>Quentin Monnet</name>
</author>
<published>2017-10-23T16:24:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a2bc2e5c2c0604bf5366b5e56ef46335adaf7491'/>
<id>urn:sha1:a2bc2e5c2c0604bf5366b5e56ef46335adaf7491</id>
<content type='text'>
Add an option parsing facility to bpftool, in prevision of future
options for demanding JSON output. Currently, two options are added:
--help and --version, that act the same as the respective commands
`help` and `version`.

Signed-off-by: Quentin Monnet &lt;quentin.monnet@netronome.com&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: add a command to display bpftool version</title>
<updated>2017-10-22T01:11:32Z</updated>
<author>
<name>Quentin Monnet</name>
</author>
<published>2017-10-19T22:46:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=821cfbb0dcfbb24506dc6958361ca2b80b928049'/>
<id>urn:sha1:821cfbb0dcfbb24506dc6958361ca2b80b928049</id>
<content type='text'>
This command can be used to print the version of the tool, which is in
fact the version from Linux taken from usr/include/linux/version.h.

Example usage:

    $ bpftool version
    bpftool v4.14.0

Signed-off-by: Quentin Monnet &lt;quentin.monnet@netronome.com&gt;
Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: show that `opcodes` or `file FILE` should be exclusive</title>
<updated>2017-10-22T01:11:32Z</updated>
<author>
<name>Quentin Monnet</name>
</author>
<published>2017-10-19T22:46:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8dfbc6d1d213df340e5dcfdcdc76ad9407a29273'/>
<id>urn:sha1:8dfbc6d1d213df340e5dcfdcdc76ad9407a29273</id>
<content type='text'>
For the `bpftool prog dump { jited | xlated } ...` command, adding
`opcodes` keyword (to request opcodes to be printed) will have no effect
if `file FILE` (to write binary output to FILE) is provided.

The manual page and the help message to be displayed in the terminal
should reflect that, and indicate that these options should be mutually
exclusive.

Signed-off-by: Quentin Monnet &lt;quentin.monnet@netronome.com&gt;
Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: use more common tag format</title>
<updated>2017-10-18T12:19:39Z</updated>
<author>
<name>Jakub Kicinski</name>
</author>
<published>2017-10-16T17:12:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2dc7c1fef9565c73c5054fd3c134afada09476c1'/>
<id>urn:sha1:2dc7c1fef9565c73c5054fd3c134afada09476c1</id>
<content type='text'>
Program tag is usually displayed as string of bytes without
any separators (e.g. as "aa5520b1090cfeb6" vs MAC addr-like
format bpftool uses currently: "aa:55:20:b1:09:0c:fe:b6").
Make bptfool use the more common format both for displaying
the tag and selecting the program by tag.

This was pointed out in review but I misunderstood the comment.

Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Reviewed-by: Simon Horman &lt;simon.horman@netronome.com&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Acked-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: use the kernel's instruction printer</title>
<updated>2017-10-10T19:30:16Z</updated>
<author>
<name>Jakub Kicinski</name>
</author>
<published>2017-10-09T17:30:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c9c35995bcf812ee8136f634c25bc6ccc3021d4c'/>
<id>urn:sha1:c9c35995bcf812ee8136f634c25bc6ccc3021d4c</id>
<content type='text'>
Compile the instruction printer from kernel/bpf and use it
for disassembling "translated" eBPF code.

Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Reviewed-by: Simon Horman &lt;simon.horman@netronome.com&gt;
Acked-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: bpftool: add documentation</title>
<updated>2017-10-05T04:46:14Z</updated>
<author>
<name>Jakub Kicinski</name>
</author>
<published>2017-10-05T03:10:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ff69c21a85a4ed3d8dcf79dd750a0a9eda4fca83'/>
<id>urn:sha1:ff69c21a85a4ed3d8dcf79dd750a0a9eda4fca83</id>
<content type='text'>
Add documentation for bpftool.  Separate files for each subcommand.
Use rst format.  Documentation is compiled into man pages using
rst2man.

Signed-off-by: David Beckett &lt;david.beckett@netronome.com&gt;
Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Acked-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
