All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@akamai.com>
To: qemu-devel@nongnu.org, linux-kernel@vger.kernel.org
Cc: mst@redhat.com, jasowang@redhat.com
Subject: [PATCH 0/2] virtio_net: allow hypervisor to indicate linkspeed and duplex setting
Date: Thu, 14 Dec 2017 14:33:51 -0500	[thread overview]
Message-ID: <cover.1513278334.git.jbaron@akamai.com> (raw)

We have found it useful to be able to set the linkspeed and duplex
settings from the host-side for virtio_net. This obviates the need
for guest changes and settings for these fields.

The ability to set linkspeed and duplex was introduced by:

16032be virtio_net: add ethtool support for set and get of settings

And using 'ethtool -s' continues to over-write the linkspeed/duplex
settings with this patch.

The 1/2 patch is against net-next, while the 2/2 patch is the associated
qemu changes that would go in after as update-linux-headers.sh should
be run first. So 2/2 is more meant as a demonstration of how I intend this
to work.

Thanks,

-Jason

Jason Baron (2):
  virtio_net: allow hypervisor to indicate linkspeed and duplex setting
  qemu: add linkspeed and duplex setting to virtio-net

 linux changes:

 drivers/net/virtio_net.c        | 11 ++++++++++-
 include/uapi/linux/virtio_net.h |  4 ++++
 2 files changed, 14 insertions(+), 1 deletion(-)

 qemu changes:

 hw/net/virtio-net.c                         | 29 +++++++++++++++++++++++++++++                                
 include/hw/virtio/virtio-net.h              |  3 +++                                                          
 include/standard-headers/linux/virtio_net.h |  4 ++++                                                         
 3 files changed, 36 insertions(+)      

-- 
2.6.1

WARNING: multiple messages have this Message-ID (diff)
From: Jason Baron <jbaron@akamai.com>
To: qemu-devel@nongnu.org, linux-kernel@vger.kernel.org
Cc: mst@redhat.com, jasowang@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] virtio_net: allow hypervisor to indicate linkspeed and duplex setting
Date: Thu, 14 Dec 2017 14:33:51 -0500	[thread overview]
Message-ID: <cover.1513278334.git.jbaron@akamai.com> (raw)

We have found it useful to be able to set the linkspeed and duplex
settings from the host-side for virtio_net. This obviates the need
for guest changes and settings for these fields.

The ability to set linkspeed and duplex was introduced by:

16032be virtio_net: add ethtool support for set and get of settings

And using 'ethtool -s' continues to over-write the linkspeed/duplex
settings with this patch.

The 1/2 patch is against net-next, while the 2/2 patch is the associated
qemu changes that would go in after as update-linux-headers.sh should
be run first. So 2/2 is more meant as a demonstration of how I intend this
to work.

Thanks,

-Jason

Jason Baron (2):
  virtio_net: allow hypervisor to indicate linkspeed and duplex setting
  qemu: add linkspeed and duplex setting to virtio-net

 linux changes:

 drivers/net/virtio_net.c        | 11 ++++++++++-
 include/uapi/linux/virtio_net.h |  4 ++++
 2 files changed, 14 insertions(+), 1 deletion(-)

 qemu changes:

 hw/net/virtio-net.c                         | 29 +++++++++++++++++++++++++++++                                
 include/hw/virtio/virtio-net.h              |  3 +++                                                          
 include/standard-headers/linux/virtio_net.h |  4 ++++                                                         
 3 files changed, 36 insertions(+)      

-- 
2.6.1

             reply	other threads:[~2017-12-14 19:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 19:33 Jason Baron [this message]
2017-12-14 19:33 ` [Qemu-devel] [PATCH 0/2] virtio_net: allow hypervisor to indicate linkspeed and duplex setting Jason Baron
2017-12-14 19:33 ` [PATCH 2/2] qemu: add linkspeed and duplex setting to virtio-net Jason Baron
2017-12-14 19:33   ` [Qemu-devel] " Jason Baron
2017-12-18 11:34   ` Yan Vugenfirer
2017-12-18 11:34     ` Yan Vugenfirer
2017-12-18 16:04     ` Jason Baron
2017-12-19  9:19       ` Yan Vugenfirer
2017-12-19 16:52         ` Jason Baron
2017-12-20 14:31           ` Michael S. Tsirkin
2017-12-20 14:32             ` Yan Vugenfirer
2017-12-20 14:33             ` Yan Vugenfirer
2017-12-21 19:42               ` Jason Baron
2017-12-21 20:40                 ` Michael S. Tsirkin
2017-12-14 19:33 ` [PATCH net-next 1/2] virtio_net: allow hypervisor to indicate linkspeed and duplex setting Jason Baron
2017-12-14 19:33   ` [Qemu-devel] " Jason Baron
2017-12-14 20:02   ` Michael S. Tsirkin
2017-12-14 20:02     ` [Qemu-devel] " Michael S. Tsirkin
2017-12-20 14:57   ` Michael S. Tsirkin
2017-12-20 14:57     ` [Qemu-devel] " Michael S. Tsirkin
2017-12-20 17:07     ` Jason Baron
2017-12-20 17:07       ` [Qemu-devel] " Jason Baron
2017-12-20 17:52       ` Michael S. Tsirkin
2017-12-20 17:52         ` [Qemu-devel] " Michael S. Tsirkin
2017-12-20 21:32         ` Jason Baron
2017-12-20 21:32           ` [Qemu-devel] " Jason Baron
2017-12-21  0:10           ` Michael S. Tsirkin
2017-12-21  0:10             ` [Qemu-devel] " Michael S. Tsirkin

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=cover.1513278334.git.jbaron@akamai.com \
    --to=jbaron@akamai.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.