qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Sameeh Jubran <sameeh@daynix.com>, qemu-devel@nongnu.org
Cc: Amnon Ilan <ailan@redhat.com>, Yan Vugenfirer <yan@daynix.com>
Subject: Re: [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu
Date: Wed, 20 Jun 2018 16:13:10 +0800	[thread overview]
Message-ID: <4f16bb8b-2061-847e-9e17-0a8f80b18197@redhat.com> (raw)
In-Reply-To: <20180619132200.12320-1-sameeh@daynix.com>



On 2018年06月19日 21:21, Sameeh Jubran wrote:
> From: Sameeh Jubran <sjubran@redhat.com>
>
> The Berkeley Packet Filter has been in the kernel for a while now and I
> think it is time that it is introduced to Qemu. This patch is an
> infrastructure for any future usage of the BPF in Qemu.
>
> It is important to note that the tun driver had started supporting using
> BPF programs through ioctls (TUNSETSTEERINGEBPF and TUNSETFILTEREBPF).
>
> At first, instead of adding the syscall wrappers, I wanted to integrate libbpf
> library which resides in the Linux source tree under tools/lib/bpf. It appears
> to be that by default it compiles to x64 on x64 arch - which can't be
> integrated into Qemu  - and my attempts to compile the 32 bit versions have
> failed. What's more interesting is that the vendors don't provide this library
> in any package, which makes this library a nasty dependency.
>
> Please share your thoughts :)

I wonder, instead of a generic eBPF support, can we have a limited but 
sufficient eBPF suppor for TAP only (see dpdk tap driver)? E.g if we 
only do bytecode loading, there's no need for e.g map update helpers.

Thanks

>
> Sameeh Jubran (1):
>    Add BPF support to qemu
>
>   MAINTAINERS                     |   7 +
>   bpf/Makefile.objs               |   1 +
>   bpf/bpf_syscall.c               |  98 ++++++
>   include/bpf/bpf_syscall.h       |  35 +++
>   linux-headers/linux/bpf.h       | 673 ++++++++++++++++++++++++++++++++++++++++
>   scripts/update-linux-headers.sh |   3 +-
>   6 files changed, 816 insertions(+), 1 deletion(-)
>   create mode 100644 bpf/Makefile.objs
>   create mode 100644 bpf/bpf_syscall.c
>   create mode 100644 include/bpf/bpf_syscall.h
>   create mode 100644 linux-headers/linux/bpf.h
>

  parent reply	other threads:[~2018-06-20  8:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 13:21 [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu Sameeh Jubran
2018-06-19 13:22 ` [Qemu-devel] [RFC 1/1] Add BPF support to qemu Sameeh Jubran
2018-06-19 14:41   ` Murilo Opsfelder Araujo
2018-06-19 14:46     ` Sameeh Jubran
2018-06-19 13:37 ` [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu Peter Maydell
2018-06-19 13:49 ` Daniel P. Berrangé
2018-06-19 14:37   ` Sameeh Jubran
2018-06-20  8:34     ` Daniel P. Berrangé
2018-06-20 14:43       ` Sameeh Jubran
2018-06-20  8:19   ` Jason Wang
2018-06-19 16:17 ` no-reply
2018-06-20  8:13 ` Jason Wang [this message]
2018-06-20 14:40   ` Sameeh Jubran

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=4f16bb8b-2061-847e-9e17-0a8f80b18197@redhat.com \
    --to=jasowang@redhat.com \
    --cc=ailan@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sameeh@daynix.com \
    --cc=yan@daynix.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 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).