From: Daniel Borkmann <daniel@iogearbox.net>
To: Adam Jackson <ajax@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Wang Nan <wangnan0@huawei.com>,
ast@kernel.org, linux-kernel@vger.kernel.org,
Li Zefan <lizefan@huawei.com>,
pi3orama@163.com, Dave Airlie <airlied@redhat.com>
Subject: Re: clang --target=bpf missing on f23 was: Re: [PATCH 1/2] perf test: Add libbpf relocation checker
Date: Fri, 22 Jan 2016 18:56:02 +0100 [thread overview]
Message-ID: <56A26D32.90806@iogearbox.net> (raw)
In-Reply-To: <1453484142.2587.7.camel@redhat.com>
On 01/22/2016 06:35 PM, Adam Jackson wrote:
> On Fri, 2016-01-22 at 14:22 -0300, Arnaldo Carvalho de Melo wrote:
>
>> the 'bpf' target for clang is being used together with perf to
>> build scriptlets into object code that then gets uploaded to the kernel
>> via sys_bpf(), was the decision not to include 'bpf' just an accident?
>
> I wouldn't call it a "decision", that would imply intent. The main
> reason I explicitly list targets for llvm is to limit the CPU backends
> to arches Fedora actually runs on (which itself is because I really
> only care about llvmpipe, and am only touching llvm because it's in my
> way). Had no idea there was a bpf backend, so never thought to enable
> it.
>
> llvm-3.7.0-4.fc2{3,4} are building now with the bpf backend enabled,
> I'll create an update for F23 when it's built.
Awesome, thanks!
next prev parent reply other threads:[~2016-01-22 17:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 9:27 [PATCH 0/2] perf bpf: Fix relocation error Wang Nan
2016-01-22 9:27 ` [PATCH 1/2] perf test: Add libbpf relocation checker Wang Nan
2016-01-22 15:40 ` Arnaldo Carvalho de Melo
2016-01-22 17:07 ` Alexei Starovoitov
2016-01-22 17:22 ` clang --target=bpf missing on f23 was: " Arnaldo Carvalho de Melo
2016-01-22 17:35 ` Adam Jackson
2016-01-22 17:42 ` Alexei Starovoitov
2016-01-22 21:09 ` David Airlie
2016-01-22 17:56 ` Daniel Borkmann [this message]
2016-01-22 19:09 ` Arnaldo Carvalho de Melo
2016-01-22 9:27 ` [PATCH 2/2] perf bpf: Check relocation target section Wang Nan
2016-01-22 17:11 ` Alexei Starovoitov
2016-01-25 1:56 ` Wangnan (F)
2016-01-25 2:04 ` Wangnan (F)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A26D32.90806@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@kernel.org \
--cc=airlied@redhat.com \
--cc=ajax@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.