linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel@iogearbox.net (Daniel Borkmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: eBPF JIT compiler
Date: Wed, 21 Jun 2017 21:53:27 +0200	[thread overview]
Message-ID: <594ACEB7.2030707@iogearbox.net> (raw)
In-Reply-To: <CAHgaXdKm6atQ=XkrQf+ShKtPU7=H+pS2VvPsTXXhz2yzOFunmA@mail.gmail.com>

On 06/21/2017 09:37 PM, Shubham Bansal wrote:
> Hi Daniel,
>
> Good news. Got the CALL to work.
>
> [  145.670882] test_bpf: Summary: 316 PASSED, 0 FAILED, [287/308 JIT'ed]
>
> Awesome. Do you think with this implementation, the patch could get
> accepted? If you think so, then I will send the patch in couple of
> days after some refactoring, if not, then do let me know what more is
> required?

Nice, it's ultimately up to the arm folks to review the set in-depth,
but feel free to send out the patch once you're done refactoring. With
BPF_CALL support that looks quite good from pov of supported insns.

  reply	other threads:[~2017-06-21 19:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 23:13 [PATCH v2] arm: eBPF JIT compiler Shubham Bansal
2017-05-25 23:23 ` Andrew Lunn
2017-05-25 23:34   ` Shubham Bansal
2017-05-25 23:36     ` Shubham Bansal
2017-05-26 16:57       ` Shubham Bansal
2017-05-30 18:50         ` Shubham Bansal
2017-05-30 19:11 ` Kees Cook
     [not found] ` <CAGXu5jKmLNMR+uhM9Ov2XPW6kCjip_SjScgEH0fTFp6fQtKFiA@mail.gmail.com>
     [not found]   ` <CAHgaXdJ=-n8J8ot_5YQC=YMZrwTBvdNTp5Ta_J_J9vNGWQ4DCQ@mail.gmail.com>
2017-06-12  2:00     ` Kees Cook
2017-06-12 10:21   ` Daniel Borkmann
2017-06-12 11:06     ` Russell King - ARM Linux
2017-06-12 15:41       ` Shubham Bansal
2017-06-12 15:40     ` Shubham Bansal
2017-06-12 22:45       ` Alexander Alemayhu
2017-06-12 22:47         ` David Miller
2017-06-12 23:17       ` Daniel Borkmann
2017-06-13  6:56       ` Shubham Bansal
2017-06-14 20:31         ` Daniel Borkmann
2017-06-17 12:23           ` Shubham Bansal
2017-06-19 18:10             ` Daniel Borkmann
2017-06-20  1:34               ` Shubham Bansal
2017-06-20 16:55                 ` Daniel Borkmann
2017-06-21 14:26                   ` Shubham Bansal
2017-06-21 16:32                     ` Daniel Borkmann
2017-06-21 19:37                       ` Shubham Bansal
2017-06-21 19:53                         ` Daniel Borkmann [this message]
     [not found]                       ` <CAHgaXdKCOM++jdoaq9PV6a_bbRU+VyuLC4KeUdYmA0gYdhmhkQ@mail.gmail.com>
2017-07-05 22:11                         ` Kees Cook
2017-07-05 22:38                           ` Kees Cook
     [not found]                             ` <CAHgaXd+ywWu6PjnqGGdyw=7=XTKm4_Ny227Eq7yH5N0s0e5YfA@mail.gmail.com>
2017-07-07  4:42                               ` Kees Cook
2017-07-07  4:49                                 ` Shubham Bansal

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=594ACEB7.2030707@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).