From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/6] tests: Add network filter tests to the check-qtest-s390x list
Date: Fri, 18 Aug 2017 10:47:02 +0200 [thread overview]
Message-ID: <09806f49-6b93-9252-4dbf-202d87d439ed@redhat.com> (raw)
In-Reply-To: <20170818095448.226fc4e9.cohuck@redhat.com>
On 18.08.2017 09:54, Cornelia Huck wrote:
> On Thu, 17 Aug 2017 16:02:00 +0200
> Thomas Huth <thuth@redhat.com> wrote:
>
>> On 17.08.2017 10:41, Cornelia Huck wrote:
[...]
>>> I'm wondering if we could unify selection of the network device
>>> somehow. There's probably two cases:
>>> - Test a specific device. This obviously needs to be decided
>>> individually.
>>> - Just use a functional network device. For s390x, this will be
>>> virtio-net-ccw; for other architectures, this test uses e1000, while
>>> one of the tests below uses rtl8139 (why?). A helper for that may be
>>> useful.
>>
>> Maybe ... OTOH, this likely increases also test coverage if we do not
>> use the same PCI NIC in all the tests...?
>
> It just looks like a bit of unneeded churn to me.
>
> Re coverage: Do we have a very simple test that we can run for all kind
> of NICs? This would give some reliable testing for various devices
> instead of having to rely on people picking different devices for their
> tests...
I think there is only the pxe-tester that comes close to a generic NIC
tester. But there are two issues:
1) You need a firmware that has a driver for the NIC
2) It's not a very fast test, so adding lots of NICs there might slow
down "make check" quite a bit.
(There are also some dedicated NIC tests available already, e.g.
tests/rtl8139-test.c tests at least some aspects of that NIC.)
Hmm, maybe we could also use a function that returns a different NIC for
the i386 and x86_64 architectures, something like:
char *get_preferred_nic_name(void)
{
const char *arch = qtest_get_arch();
if (g_str_equal(arch, "i386")) {
return "rtl8139";
} else if (g_str_equal(arch, "s390x")) {
return "virtio-net-ccw";
} else if (g_str_equal(arch, "ppc64")) {
return "spapr-vlan";
} else {
return "e1000";
}
}
That way, we'd also get test coverage for both, e1000 and rtl8139... ?
Thomas
next prev parent reply other threads:[~2017-08-18 8:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 6:25 [Qemu-devel] [PATCH for-2.11 0/6] Enable more qtests for s390x Thomas Huth
2017-08-17 6:25 ` [Qemu-devel] [PATCH 1/6] tests: Run filter-redirector and -mirror test only on POSIX systems Thomas Huth
2017-08-17 8:25 ` Cornelia Huck
2017-08-17 9:41 ` David Hildenbrand
2017-08-17 10:09 ` Zhang Chen
2017-08-30 19:35 ` Cleber Rosa
2017-08-17 6:25 ` [Qemu-devel] [PATCH 2/6] tests: Add network filter tests to the check-qtest-s390x list Thomas Huth
2017-08-17 8:41 ` Cornelia Huck
2017-08-17 14:02 ` Thomas Huth
2017-08-18 1:49 ` Zhang Chen
2017-08-18 7:54 ` Cornelia Huck
2017-08-18 8:47 ` Thomas Huth [this message]
2017-08-30 20:05 ` Cleber Rosa
2017-08-30 20:03 ` Cleber Rosa
2017-08-17 6:25 ` [Qemu-devel] [PATCH 3/6] tests: Enable the drive_del test also on s390x Thomas Huth
2017-08-17 8:53 ` Cornelia Huck
2017-08-17 9:46 ` David Hildenbrand
2017-08-17 13:54 ` Thomas Huth
2017-08-17 14:01 ` Cornelia Huck
2017-08-30 21:41 ` Cleber Rosa
2017-09-04 13:49 ` Cornelia Huck
2017-08-17 6:25 ` [Qemu-devel] [PATCH 4/6] tests: Introduce generic device hot-plug/hot-unplug functions Thomas Huth
2017-08-17 9:00 ` Cornelia Huck
2017-08-17 9:53 ` David Hildenbrand
2017-08-17 10:57 ` Thomas Huth
2017-08-17 11:16 ` David Hildenbrand
2017-08-17 6:25 ` [Qemu-devel] [PATCH 5/6] tests: Add qvirtio_(un)plug_device_test wrapper functions Thomas Huth
2017-08-17 9:04 ` Cornelia Huck
2017-08-17 6:25 ` [Qemu-devel] [PATCH 6/6] tests: Enable the simple virtio tests on s390x, too Thomas Huth
2017-08-17 9:07 ` Cornelia Huck
2017-08-17 9:11 ` [Qemu-devel] [PATCH for-2.11 0/6] Enable more qtests for s390x Cornelia Huck
2017-08-18 13:40 ` Cornelia Huck
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=09806f49-6b93-9252-4dbf-202d87d439ed@redhat.com \
--to=thuth@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).