All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org, laine@redhat.com,
	mst@redhat.com
Subject: Re: [Qemu-devel] Libvirt support of mac-programming over macvtap planned?
Date: Mon, 4 Nov 2013 15:34:37 +0800	[thread overview]
Message-ID: <20131104073437.GA22744@amosk.info> (raw)
In-Reply-To: <20131030051832.GB1839@amosk.info>


> Laine Stump wrote:
> On 10/30/2013 07:18 AM, Amos Kong wrote:
> > On Tue, Oct 29, 2013 at 09:50:56AM -0400, Matthew Rosato wrote:
> >> Amos Kong provided QEMU support to facilitate macvtap rx-filter change
> >> notification here:
> >> http://lists.nongnu.org/archive/html/qemu-devel/2013-07/msg02736.html
> >>
> >> Libvirt work was mentioned, but I haven't noticed any activity here
> >> regarding exploitation -- Is someone working this or planning to in the
> >> near future?  Don't want to duplicate effort.  Anything that I can do to
> >> help?
> 
> We are interested in it, but nobody has had the free time to do the work
> yet. I'd be happy to point you in the right direction if you have the
> cycles available to work on it.
> 
> (I'm curious where your original query was sent - I didn't see it in my
> libvir-list nor my qemu-devel folders...)

The v3 is here: http://lists.nongnu.org/archive/html/qemu-devel/2013-05/msg03075.html

       reply	other threads:[~2013-11-04  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <526FBD40.5010206@linux.vnet.ibm.com>
     [not found] ` <20131030051832.GB1839@amosk.info>
2013-11-04  7:34   ` Amos Kong [this message]
2013-11-04 11:48     ` [Qemu-devel] [libvirt] Libvirt support of mac-programming over macvtap planned? Viktor Mihajlovski

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=20131104073437.GA22744@amosk.info \
    --to=akong@redhat.com \
    --cc=laine@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=mjrosato@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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.