From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] net: add net_is_tap_client()
Date: Thu, 18 Oct 2012 17:48:55 +0200 [thread overview]
Message-ID: <20121018154855.GA3656@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <50801ACF.50203@redhat.com>
On Thu, Oct 18, 2012 at 05:05:51PM +0200, Paolo Bonzini wrote:
> Il 18/10/2012 16:56, Stefan Hajnoczi ha scritto:
> > From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> >
> > The vhost-net code interacts closely with the net/tap.c backend so that
> > it can pass the underlying file descriptor to the vhost_net.ko driver.
> > We need a check that confirms a NetClientState is indeed a tap backend
> > (and not something else like slirp or socket).
>
> Could you use object_dynamic_cast(OBJECT(backend), TYPE_TAP_NET_CLIENT)
> instead?
Yes.
Stefan
next prev parent reply other threads:[~2012-10-18 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 14:56 [Qemu-devel] [PATCH 0/4] net: convert NetClientState to QOM Stefan Hajnoczi
2012-10-18 14:56 ` [Qemu-devel] [PATCH 1/4] net: add public qemu_net_poll() function Stefan Hajnoczi
2012-10-18 14:56 ` [Qemu-devel] [PATCH 2/4] net: add net_is_tap_client() Stefan Hajnoczi
2012-10-18 15:05 ` Paolo Bonzini
2012-10-18 15:48 ` Stefan Hajnoczi [this message]
2012-10-18 14:56 ` [Qemu-devel] [PATCH 3/4] net: extract notify_link_status_changed() function Stefan Hajnoczi
2012-10-18 14:56 ` [Qemu-devel] [PATCH 4/4] net: convert NetClientState to QOM Stefan Hajnoczi
2012-10-18 15:06 ` Paolo Bonzini
2012-10-19 7:38 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 10:56 [Qemu-devel] [PATCH 0/4] " Stefan Hajnoczi
2012-07-02 10:56 ` [Qemu-devel] [PATCH 2/4] net: add net_is_tap_client() Stefan Hajnoczi
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=20121018154855.GA3656@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).