qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Shannon Zhao <shannon.zhao@linaro.org>
Cc: peter.maydell@linaro.org, hangaohuai@huawei.com, mst@redhat.com,
	peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
	zhaoshenglong@huawei.com, pbonzini@redhat.com,
	christoffer.dall@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 1/2] hw/net/virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net
Date: Tue, 21 Apr 2015 09:30:25 +0200	[thread overview]
Message-ID: <20150421093025.4a64d51e.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <5535AB48.6010808@linaro.org>

On Tue, 21 Apr 2015 09:43:36 +0800
Shannon Zhao <shannon.zhao@linaro.org> wrote:

> On 2015/4/20 19:32, Cornelia Huck wrote:
> > On Mon, 20 Apr 2015 16:20:00 +0800
> > shannon.zhao@linaro.org wrote:
> > 
> >> From: Shannon Zhao <shannon.zhao@linaro.org>
> >>
> >> Move DEFINE_VIRTIO_NET_FEATURES to the backend virtio-net.
> >> The transports just sync the host features from backend.
> >>
> >> Signed-off-by: Shannon Zhao <zhaoshenglong@huawei.com>
> >> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
> >> ---
> >>  hw/net/virtio-net.c            | 4 ++++
> >>  hw/s390x/s390-virtio-bus.c     | 1 -
> >>  hw/s390x/virtio-ccw.c          | 1 -
> >>  hw/virtio/virtio-pci.c         | 1 -
> >>  include/hw/virtio/virtio-net.h | 1 +
> >>  5 files changed, 5 insertions(+), 3 deletions(-)
> > 
> > I need the following change to make this work for virtio-ccw:
> >
> 
> 
> Maybe we can use following patch. This moves virtio_net_set_config_size to
> virtio_net_device_realize function. As the features are moved to virtio-net,
> so we should set the config_size in virtio-net too. And this can be useful to
> virtio-mmio which now doesn't call virtio_net_set_config_size in
> virtio-mmio's realize function.

I think this makes sense.

> 
> Cornelia, could you check if this works on s390? Thanks.

Networking works again via virtio-ccw with this patch on top.

I'll still try to figure out a better sequence for realizing/plugging
virtio-ccw devices, but I think that is orthogonal to this patch.

  reply	other threads:[~2015-04-21  7:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  8:19 [Qemu-devel] [PATCH v2 0/2] virtio: Move host features to backends shannon.zhao
2015-04-20  8:20 ` [Qemu-devel] [PATCH v2 1/2] hw/net/virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net shannon.zhao
2015-04-20  9:20   ` Cornelia Huck
2015-04-20 11:32   ` Cornelia Huck
2015-04-20 13:32     ` Shannon Zhao
2015-04-20 14:08       ` Cornelia Huck
2015-04-20 14:34         ` Peter Maydell
2015-04-20 16:44           ` Cornelia Huck
2015-04-21  1:43     ` Shannon Zhao
2015-04-21  7:30       ` Cornelia Huck [this message]
2015-04-21 10:33         ` Shannon Zhao
2015-04-20  8:20 ` [Qemu-devel] [PATCH v2 2/2] virtio-scsi: Move DEFINE_VIRTIO_SCSI_FEATURES to virtio-scsi shannon.zhao

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=20150421093025.4a64d51e.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=hangaohuai@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.org \
    --cc=zhaoshenglong@huawei.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).