From: Ilya Maximets <i.maximets@samsung.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
dev@dpdk.org, David Marchand <david.marchand@redhat.com>
Cc: Tiwei Bie <tiwei.bie@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Ian Stokes <ian.stokes@intel.com>,
Kevin Traynor <ktraynor@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] IOPL related fixes
Date: Fri, 23 Nov 2018 18:53:56 +0300 [thread overview]
Message-ID: <69a9bf2c-7664-4e63-48a4-fe2f73ce3c86@samsung.com> (raw)
In-Reply-To: <4b4f7faf-fb21-74d6-f76e-105ba78ff59c@redhat.com>
On 23.11.2018 18:41, Maxime Coquelin wrote:
> Hi,
>
> On 11/23/18 4:39 PM, Ilya Maximets wrote:
>> Patches primary targeted to fix OVS unit test failures with
>> DPDK 18.11 due to following error:
>> 'IOPL call failed - cannot use virtio PMD'.
>
> You mention v18.11, do you mean this is a regression?
Kind of. But not really a bug. It's just a message that shows up
every time you starting the app as a non-root user.
The message itself was introduced long time ago, but it wasn't
printed for unclear reasons. It's probably some change in logging
subsystem uncovered it.
I just checked and found that message appears starting from v18.02.
But OVS stuck with 17.11 LTS where this message exists, but not
printed for some reason. That's why this wasn't an issue previously.
P.S. OVS tests just checks the output for error messages.
Tests themselves works fine. They are not actually using DPDK.
Best regards, Ilya Maximets.
>
>>
>> We can avoid test failures in OVS by filtering the output like this:
>> https://patchwork.ozlabs.org/project/openvswitch/list/?series=77706
>> but it still looks very inconvenient for me to have this
>> message in the output of every command for the DPDK linked app.
>>
>> Version 3:
>> * Splitted in two patches. [David Marchand]
>> * Fixed typo in commit message. [David Marchand]
>>
>> Version 2:
>> * Fixed possible fd leak on BSD.
>>
>> Ilya Maximets (2):
>> eal/bsd: fix possible IOPL fd leak
>> net/virtio: avoid annoying IOPL call related errors
>>
>> drivers/net/virtio/virtio_ethdev.c | 11 ++++++-----
>> lib/librte_eal/bsdapp/eal/eal.c | 6 ++++--
>> 2 files changed, 10 insertions(+), 7 deletions(-)
>>
>
>
next prev parent reply other threads:[~2018-11-23 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181123141748eucas1p132a221972a87ec82b50d4a6c83bd9646@eucas1p1.samsung.com>
2018-11-23 14:17 ` [dpdk-dev] [PATCH] net/virtio: avoid annoying IOPL call related errors Ilya Maximets
[not found] ` <CGME20181123143625eucas1p1def3421fa13b5aec7204549932c75bb7@eucas1p1.samsung.com>
2018-11-23 14:36 ` [dpdk-dev] [PATCH v2] " Ilya Maximets
2018-11-23 15:02 ` David Marchand
[not found] ` <CGME20181123153936eucas1p13bfbe13fcda92de7760ac768fcab43c5@eucas1p1.samsung.com>
2018-11-23 15:39 ` [dpdk-dev] [PATCH v3 0/2] IOPL related fixes Ilya Maximets
[not found] ` <CGME20181123153947eucas1p169a2b7cec02b2edd7258aef11b1c1e2e@eucas1p1.samsung.com>
2018-11-23 15:39 ` [dpdk-dev] [PATCH v3 1/2] eal/bsd: fix possible IOPL fd leak Ilya Maximets
2018-11-23 17:32 ` Maxime Coquelin
[not found] ` <CGME20181123153951eucas1p1218331b7e51db8eae3073fa6a14f3bcd@eucas1p1.samsung.com>
2018-11-23 15:39 ` [dpdk-dev] [PATCH v3 2/2] net/virtio: avoid annoying IOPL call related errors Ilya Maximets
2018-11-23 17:34 ` Maxime Coquelin
2018-11-23 15:41 ` [dpdk-dev] [PATCH v3 0/2] IOPL related fixes Maxime Coquelin
2018-11-23 15:53 ` Ilya Maximets [this message]
2018-11-23 16:25 ` Maxime Coquelin
2018-11-23 20:07 ` Kevin Traynor
2018-11-23 22:29 ` Thomas Monjalon
2018-11-25 10:42 ` Thomas Monjalon
2018-11-26 9:49 ` Kevin Traynor
2018-11-27 14:05 ` David Marchand
2018-11-23 17:15 ` [dpdk-dev] [PATCH v2] net/virtio: avoid annoying IOPL call related errors Timothy Redaelli
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=69a9bf2c-7664-4e63-48a4-fe2f73ce3c86@samsung.com \
--to=i.maximets@samsung.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ian.stokes@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@intel.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).