[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170413.130415.1776516439699504044.davem@davemloft.net>
Date: Thu, 13 Apr 2017 13:04:15 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: david.daney@...ium.com
Cc: ast@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools: bpf_jit_disasm: Add option to dump JIT image to
a file.
From: David Daney <david.daney@...ium.com>
Date: Tue, 11 Apr 2017 14:30:52 -0700
> When debugging the JIT on an embedded platform or cross build
> environment, libbfd may not be available, making it impossible to run
> bpf_jit_disasm natively.
>
> Add an option to emit a binary image of the JIT code to a file. This
> file can then be disassembled off line. Typical usage in this case
> might be (pasting mips64 dmesg output to cat command):
>
> $ cat > jit.raw
> $ bpf_jit_disasm -f jit.raw -O jit.bin
> $ mips64-linux-gnu-objdump -D -b binary -m mips:isa64r2 -EB jit.bin
>
> Signed-off-by: David Daney <david.daney@...ium.com>
Applied, thanks.
Powered by blists - more mailing lists