From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: pkrempa@redhat.com, berrange@redhat.com, ehabkost@redhat.com,
aadam@redhat.com, qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>,
laine@redhat.com, ailan@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] add failover feature for assigned network devices
Date: Thu, 30 May 2019 14:12:21 -0400 [thread overview]
Message-ID: <20190530141112-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190529074802.2cofzjkudfuilbej@jenstp.localdomain>
On Wed, May 29, 2019 at 09:48:02AM +0200, Jens Freimann wrote:
> On Tue, May 28, 2019 at 10:40:42PM -0400, Michael S. Tsirkin wrote:
> > On Tue, May 21, 2019 at 08:49:18PM +0200, Jens Freimann wrote:
> > > On Tue, May 21, 2019 at 07:37:19AM -0400, Michael S. Tsirkin wrote:
> > > > On Tue, May 21, 2019 at 09:21:57AM +0200, Jens Freimann wrote:
> > > > Actually is there a list of devices for which this has been tested
> > > > besides mlx5? I think someone said some old intel cards
> > > > don't support this well, we might need to blacklist these ...
> > >
> > > So far I've tested mlx5 and XL710 which both worked, but I'm
> > > working on testing with more devices. But of course help with testing
> > > is greatly appreciated.
> >
> > A testing tool that people can run to get a pass/fail
> > result would be needed for that.
> > Do you have something like this?
>
> I have two simple tools. One that sends packets and another one that
> sniffs for packets to see which device the packet goes to. Find it at
> https://github.com/jensfr/netfailover_driver_detect
>
> Feedback and/or patches welcome.
>
> regards,
> Jens
The docs say:
./is_legacy -d . If is_legacy returns 0 it means it has received the packets sent by send_packet. If it returns 1 it didn't receive the packet. Now run ./is_legacy -d
So -d twice. What is the difference?
--
MST
next prev parent reply other threads:[~2019-05-30 18:13 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 12:58 [Qemu-devel] [PATCH 0/4] add failover feature for assigned network devices Jens Freimann
2019-05-17 12:58 ` [Qemu-devel] [PATCH 1/4] migration: allow unplug during migration for failover devices Jens Freimann
2019-05-21 9:33 ` Dr. David Alan Gilbert
2019-05-21 9:47 ` Daniel P. Berrangé
2019-05-23 8:01 ` Jens Freimann
2019-05-23 15:37 ` Dr. David Alan Gilbert
2019-05-17 12:58 ` [Qemu-devel] [PATCH 2/4] qdev/qbus: Add hidden device support Jens Freimann
2019-05-21 11:33 ` Michael S. Tsirkin
2019-05-17 12:58 ` [Qemu-devel] [PATCH 3/4] net/virtio: add failover support Jens Freimann
2019-05-21 9:45 ` Dr. David Alan Gilbert
2019-05-30 14:56 ` Jens Freimann
2019-05-30 17:46 ` Michael S. Tsirkin
2019-05-30 18:00 ` Dr. David Alan Gilbert
2019-05-30 18:09 ` Michael S. Tsirkin
2019-05-30 18:22 ` Eduardo Habkost
2019-05-30 23:06 ` Michael S. Tsirkin
2019-05-31 17:01 ` Eduardo Habkost
2019-05-31 18:04 ` Michael S. Tsirkin
2019-05-31 18:42 ` Eduardo Habkost
2019-05-31 18:45 ` Dr. David Alan Gilbert
2019-05-31 20:29 ` Alex Williamson
2019-05-31 21:05 ` Michael S. Tsirkin
2019-05-31 21:59 ` Eduardo Habkost
2019-06-03 8:59 ` Dr. David Alan Gilbert
2019-05-31 20:43 ` Michael S. Tsirkin
2019-05-31 21:03 ` Eduardo Habkost
2019-06-03 8:06 ` Dr. David Alan Gilbert
2019-05-30 19:08 ` Dr. David Alan Gilbert
2019-05-30 19:21 ` Michael S. Tsirkin
2019-05-31 8:23 ` Dr. David Alan Gilbert
2019-06-05 15:23 ` Daniel P. Berrangé
2019-05-30 18:17 ` Eduardo Habkost
2019-05-30 19:09 ` Dr. David Alan Gilbert
2019-05-31 21:47 ` Eduardo Habkost
2019-06-03 8:24 ` Jens Freimann
2019-06-03 9:26 ` Jens Freimann
2019-06-03 18:10 ` Laine Stump
2019-06-03 18:46 ` Alex Williamson
2019-06-05 15:20 ` Daniel P. Berrangé
2019-06-06 15:00 ` Roman Kagan
2019-06-03 19:36 ` Eduardo Habkost
2019-06-04 13:43 ` Jens Freimann
2019-06-04 14:09 ` Eduardo Habkost
2019-06-04 17:06 ` Michael S. Tsirkin
2019-06-04 19:00 ` Dr. David Alan Gilbert
2019-06-07 14:14 ` Jens Freimann
2019-06-07 14:32 ` Michael S. Tsirkin
2019-06-07 17:51 ` Dr. David Alan Gilbert
2019-06-05 14:36 ` Daniel P. Berrangé
2019-06-05 16:04 ` Laine Stump
2019-06-05 16:19 ` Daniel P. Berrangé
2019-05-17 12:58 ` [Qemu-devel] [PATCH 4/4] vfio/pci: unplug failover primary device before migration Jens Freimann
2019-05-20 22:56 ` [Qemu-devel] [PATCH 0/4] add failover feature for assigned network devices Alex Williamson
2019-05-21 7:21 ` Jens Freimann
2019-05-21 11:37 ` Michael S. Tsirkin
2019-05-21 18:49 ` Jens Freimann
2019-05-29 0:14 ` si-wei liu
2019-05-29 2:54 ` Michael S. Tsirkin
2019-06-03 18:06 ` Laine Stump
2019-06-03 18:12 ` Michael S. Tsirkin
2019-06-03 18:18 ` Laine Stump
2019-06-06 21:49 ` Michael S. Tsirkin
2019-05-29 2:40 ` Michael S. Tsirkin
2019-05-29 7:48 ` Jens Freimann
2019-05-30 18:12 ` Michael S. Tsirkin [this message]
2019-05-31 15:12 ` Jens Freimann
2019-05-21 14:18 ` Alex Williamson
2019-05-21 8:37 ` Daniel P. Berrangé
2019-05-21 10:10 ` Michael S. Tsirkin
2019-05-21 19:17 ` Jens Freimann
2019-05-21 21:43 ` Michael S. Tsirkin
2019-06-11 15:42 ` Laine Stump
2019-06-11 15:51 ` Michael S. Tsirkin
2019-06-11 16:12 ` Laine Stump
2019-06-12 9:11 ` Daniel P. Berrangé
2019-06-12 11:59 ` Jens Freimann
2019-06-12 15:54 ` Laine Stump
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=20190530141112-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aadam@redhat.com \
--cc=ailan@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jfreimann@redhat.com \
--cc=laine@redhat.com \
--cc=pkrempa@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).