From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Borkmann <daniel@iogearbox.net>, davem@davemloft.net
Cc: holzheu@linux.vnet.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] test_bpf: assign type to native eBPF test cases
Date: Thu, 30 Jul 2015 10:14:13 -0700 [thread overview]
Message-ID: <55BA5B65.4040902@plumgrid.com> (raw)
In-Reply-To: <45cfb718190f86817a7662e58499a08f30521404.1438250937.git.daniel@iogearbox.net>
On 7/30/15 3:42 AM, Daniel Borkmann wrote:
> As JITs start to perform optimizations whether to clear A and X on eBPF
> programs in the prologue, we should actually assign a program type to the
> native eBPF test cases. It doesn't really matter which program type, as
> these instructions don't go through the verifier, but it needs to be a
> type != BPF_PROG_TYPE_UNSPEC. This reflects eBPF programs loaded via bpf(2)
> system call (!= type unspec) vs. classic BPF to eBPF migrations (== type
> unspec).
>
> Signed-off-by: Daniel Borkmann<daniel@iogearbox.net>
> Cc: Michael Holzheu<holzheu@linux.vnet.ibm.com>
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
next prev parent reply other threads:[~2015-07-30 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 10:42 [PATCH net-next 0/4] Minor BPF updates Daniel Borkmann
2015-07-30 10:42 ` [PATCH net-next 1/4] test_bpf: assign type to native eBPF test cases Daniel Borkmann
2015-07-30 17:14 ` Alexei Starovoitov [this message]
2015-07-30 10:42 ` [PATCH net-next 2/4] bpf: provide helper that indicates eBPF was migrated Daniel Borkmann
2015-07-30 17:15 ` Alexei Starovoitov
2015-07-30 10:42 ` [PATCH net-next 3/4] bpf, x86/sparc: show actual number of passes in bpf_jit_dump Daniel Borkmann
2015-07-30 17:15 ` Alexei Starovoitov
2015-07-30 10:42 ` [PATCH net-next 4/4] bpf: also show process name/pid " Daniel Borkmann
2015-07-30 17:18 ` Alexei Starovoitov
2015-07-30 18:13 ` [PATCH net-next 0/4] Minor BPF updates David Miller
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=55BA5B65.4040902@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=holzheu@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
/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.