From: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: mst@redhat.com, stephen@networkplumber.org, davem@davemloft.net,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
virtio-dev@lists.oasis-open.org, jesse.brandeburg@intel.com,
alexander.h.duyck@intel.com, kubakici@wp.pl, jasowang@redhat.com,
loseweigh@gmail.com, aaron.f.brown@intel.com
Subject: Re: [PATCH net-next v9 1/4] virtio_net: Introduce VIRTIO_NET_F_STANDBY feature bit
Date: Sun, 29 Apr 2018 19:47:03 -0700 [thread overview]
Message-ID: <9826909e-d6cd-a0a3-142f-6f7f8cf2b5ce@intel.com> (raw)
In-Reply-To: <20180428075027.GI5632@nanopsycho.orion>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On 4/28/2018 12:50 AM, Jiri Pirko wrote:
> Fri, Apr 27, 2018 at 07:06:57PM CEST,sridhar.samudrala@intel.com wrote:
>> This feature bit can be used by hypervisor to indicate virtio_net device to
>> act as a standby for another device with the same MAC address.
>>
>> VIRTIO_NET_F_STANDBY is defined as bit 62 as it is a device feature bit.
>>
>> Signed-off-by: Sridhar Samudrala<sridhar.samudrala@intel.com>
>> ---
>> drivers/net/virtio_net.c | 2 +-
>> include/uapi/linux/virtio_net.h | 3 +++
>> 2 files changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 3b5991734118..51a085b1a242 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -2999,7 +2999,7 @@ static struct virtio_device_id id_table[] = {
>> VIRTIO_NET_F_GUEST_ANNOUNCE, VIRTIO_NET_F_MQ, \
>> VIRTIO_NET_F_CTRL_MAC_ADDR, \
>> VIRTIO_NET_F_MTU, VIRTIO_NET_F_CTRL_GUEST_OFFLOADS, \
>> - VIRTIO_NET_F_SPEED_DUPLEX
>> + VIRTIO_NET_F_SPEED_DUPLEX, VIRTIO_NET_F_STANDBY
> This is not part of current qemu master (head 6f0c4706b35dead265509115ddbd2a8d1af516c1)
> Were I can find the qemu code?
>
> Also, I think it makes sense to push HW (qemu HW in this case) first
> and only then the driver.
I had sent qemu patch with a couple of earlier versions of this patchset.
Will include it when i send out v10.
[-- Attachment #2: Type: text/html, Size: 1897 bytes --]
next prev parent reply other threads:[~2018-04-30 2:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 17:06 [PATCH net-next v9 0/4] Enable virtio_net to act as a standby for a passthru device Sridhar Samudrala
2018-04-27 17:06 ` [PATCH net-next v9 1/4] virtio_net: Introduce VIRTIO_NET_F_STANDBY feature bit Sridhar Samudrala
2018-04-28 7:50 ` Jiri Pirko
2018-04-30 2:47 ` Samudrala, Sridhar [this message]
2018-04-30 7:03 ` Jiri Pirko
2018-04-30 19:14 ` Samudrala, Sridhar
2018-04-27 17:06 ` [PATCH net-next v9 2/4] net: Introduce generic failover module Sridhar Samudrala
2018-04-27 17:53 ` Jiri Pirko
2018-04-28 8:15 ` Jiri Pirko
2018-04-30 2:47 ` Samudrala, Sridhar
2018-04-28 9:06 ` Jiri Pirko
2018-04-30 3:03 ` Samudrala, Sridhar
2018-05-02 16:15 ` Jiri Pirko
2018-05-02 17:51 ` Samudrala, Sridhar
2018-05-02 20:30 ` Michael S. Tsirkin
2018-05-02 21:36 ` Samudrala, Sridhar
2018-05-02 21:39 ` Jiri Pirko
2018-05-02 21:39 ` Jiri Pirko
2018-04-27 17:06 ` [PATCH net-next v9 3/4] virtio_net: Extend virtio to use VF datapath when available Sridhar Samudrala
2018-04-28 8:24 ` Jiri Pirko
2018-04-30 3:00 ` Samudrala, Sridhar
2018-04-30 7:12 ` Jiri Pirko
2018-04-30 19:26 ` Samudrala, Sridhar
2018-05-01 7:33 ` Jiri Pirko
2018-04-28 9:42 ` Jiri Pirko
2018-04-29 8:56 ` Siwei Liu
2018-04-29 13:45 ` Jiri Pirko
2018-04-30 4:16 ` Samudrala, Sridhar
2018-04-30 7:20 ` Jiri Pirko
2018-05-02 0:20 ` Samudrala, Sridhar
2018-05-02 7:50 ` Jiri Pirko
2018-05-02 15:34 ` Samudrala, Sridhar
2018-05-02 16:05 ` Jiri Pirko
2018-05-02 15:47 ` Michael S. Tsirkin
2018-05-02 16:04 ` Jiri Pirko
2018-04-27 17:07 ` [PATCH net-next v9 4/4] netvsc: refactor notifier/event handling code to use the failover framework Sridhar Samudrala
2018-04-27 17:45 ` [PATCH net-next v9 0/4] Enable virtio_net to act as a standby for a passthru device Jiri Pirko
2018-04-27 17:53 ` Samudrala, Sridhar
2018-04-27 19:38 ` Jiri Pirko
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=9826909e-d6cd-a0a3-142f-6f7f8cf2b5ce@intel.com \
--to=sridhar.samudrala@intel.com \
--cc=aaron.f.brown@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kubakici@wp.pl \
--cc=loseweigh@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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).