From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
lersek@redhat.com, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/4] net: convert NetClientState to QOM
Date: Mon, 2 Jul 2012 11:56:49 +0100 [thread overview]
Message-ID: <1341226613-15577-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
Note: These patches apply on top of Zhi Yong Wu's vlan-hub v6 and -netdev
socket v2 series.
This series is the first step in QOMifying the net subsystem. These patches
make NetClientState an Object so that all -netdev and NICs use QOM. The net
clients are not yet visible in the QOM tree and have no properties.
I wanted to send this out before I go on vacation 3 - 11 July since others are
making changes in the net subsystem and this could conflict.
Future patch series will focus on:
1. QOM lifecycle for NetClientState, including dealing with hotplug.
2. QOM properties for each -netdev type.
3. Exposing net clients in the QOM tree.
4. Replacing ad-hoc code with QOM usage.
Stefan Hajnoczi (4):
net: add public qemu_net_poll() function
net: add net_is_tap_client()
net: extract notify_link_status_changed() function
net: convert NetClientState to QOM
hw/cadence_gem.c | 27 +++++++---
hw/dp8393x.c | 41 ++++++++++----
hw/e1000.c | 32 +++++++----
hw/eepro100.c | 27 +++++++---
hw/etraxfs_eth.c | 27 +++++++---
hw/lan9118.c | 27 +++++++---
hw/lance.c | 18 +------
hw/mcf_fec.c | 32 ++++++++---
hw/milkymist-minimac2.c | 26 ++++++---
hw/mipsnet.c | 25 ++++++---
hw/musicpal.c | 26 ++++++---
hw/ne2000-isa.c | 17 +-----
hw/ne2000.c | 23 +++++---
hw/ne2000.h | 2 +
hw/opencores_eth.c | 28 +++++++---
hw/pcnet-pci.c | 18 +------
hw/pcnet.c | 36 +++++++++++--
hw/pcnet.h | 3 +-
hw/rtl8139.c | 26 ++++++---
hw/smc91c111.c | 26 ++++++---
hw/spapr_llan.c | 24 ++++++---
hw/stellaris_enet.c | 26 ++++++---
hw/usb/dev-network.c | 25 ++++++---
hw/vhost_net.c | 11 ++--
hw/virtio-net.c | 43 ++++++++++-----
hw/xen_nic.c | 29 +++++++---
hw/xgmac.c | 26 ++++++---
hw/xilinx_axienet.c | 26 ++++++---
hw/xilinx_ethlite.c | 26 ++++++---
net.c | 138 ++++++++++++++++++++++++++++++++---------------
net.h | 35 ++++++++----
net/dump.c | 30 ++++++++---
net/hub.c | 51 +++++++++++-------
net/slirp.c | 29 +++++++---
net/socket.c | 80 +++++++++++++++------------
net/tap-win32.c | 29 ++++++++--
net/tap.c | 83 ++++++++++++++++------------
net/tap.h | 1 +
net/vde.c | 28 ++++++++--
39 files changed, 841 insertions(+), 386 deletions(-)
--
1.7.10
next reply other threads:[~2012-07-02 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 10:56 Stefan Hajnoczi [this message]
2012-07-02 10:56 ` [Qemu-devel] [PATCH 1/4] net: add public qemu_net_poll() function Stefan Hajnoczi
2012-07-02 10:56 ` [Qemu-devel] [PATCH 2/4] net: add net_is_tap_client() Stefan Hajnoczi
2012-07-02 10:56 ` [Qemu-devel] [PATCH 3/4] net: extract notify_link_status_changed() function Stefan Hajnoczi
2012-07-02 10:56 ` [Qemu-devel] [PATCH 4/4] net: convert NetClientState to QOM Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 14:56 [Qemu-devel] [PATCH 0/4] " 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=1341226613-15577-1-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=lersek@redhat.com \
--cc=pbonzini@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 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).