qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Sameeh Jubran <sameeh@daynix.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
	Yan Vugenfirer <yan@daynix.com>, Amnon Ilan <ailan@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu
Date: Tue, 19 Jun 2018 14:49:33 +0100	[thread overview]
Message-ID: <20180619134933.GY20929@redhat.com> (raw)
In-Reply-To: <20180619132200.12320-1-sameeh@daynix.com>

On Tue, Jun 19, 2018 at 04:21:59PM +0300, 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 :)

IMHO there should be example usage illustrated for some part of QEMU
before we add any general infrastructure, as you can't really do a
useful design evaluation without understanding its usage.

It isn't clear that QEMU is neccessarily the best place to even do it, if
the intended usage is to provide network traffic firewalling for guest
NICs. eg libvirt already provides a firewalling system based on iptables,
that could have an BPFilter implementation added to it.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  parent reply	other threads:[~2018-06-19 13:49 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é [this message]
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
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=20180619134933.GY20929@redhat.com \
    --to=berrange@redhat.com \
    --cc=ailan@redhat.com \
    --cc=jasowang@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).