Message ID | 20181123153920.12398-1-i.maximets@samsung.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F37561B58D; Fri, 23 Nov 2018 16:39:39 +0100 (CET) Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) by dpdk.org (Postfix) with ESMTP id 345111B57B for <dev@dpdk.org>; Fri, 23 Nov 2018 16:39:38 +0100 (CET) Received: from eucas1p2.samsung.com (unknown [182.198.249.207]) by mailout1.w1.samsung.com (KnoxPortal) with ESMTP id 20181123153938euoutp0160c70ef16d2253119178f74deea519be~pywb2rblY0551305513euoutp01Z for <dev@dpdk.org>; Fri, 23 Nov 2018 15:39:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20181123153938euoutp0160c70ef16d2253119178f74deea519be~pywb2rblY0551305513euoutp01Z DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1542987578; bh=be4ciH6DoWxpzlQImfSS34FouKY0SV7++HG6CXUCXX4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ujg/fol9YbC92dHTJvNKplubGuuF39mUHVQLS2duPFuhkuMVYYYh1ZRb9+DRaKno9 exVM8OB7LeNI2ImTIY1cZYCoY0mnp+DZgUS0cmu6ngr8hFujEuG5qzUVS+cWE5f1yE a2nQITXMCb8oBBmb08JvWkkIOb4t+gbtxIC0uxMI= Received: from eusmges1new.samsung.com (unknown [203.254.199.242]) by eucas1p1.samsung.com (KnoxPortal) with ESMTP id 20181123153937eucas1p1abd3fbd07eebd9e5f76dbea969d70216~pywbcRa7_2386523865eucas1p16; Fri, 23 Nov 2018 15:39:37 +0000 (GMT) Received: from eucas1p1.samsung.com ( [182.198.249.206]) by eusmges1new.samsung.com (EUCPMTA) with SMTP id A9.A8.04441.93F18FB5; Fri, 23 Nov 2018 15:39:37 +0000 (GMT) Received: from eusmtrp2.samsung.com (unknown [182.198.249.139]) by eucas1p1.samsung.com (KnoxPortal) with ESMTPA id 20181123153936eucas1p13bfbe13fcda92de7760ac768fcab43c5~pywarTu8j0118701187eucas1p1D; Fri, 23 Nov 2018 15:39:36 +0000 (GMT) Received: from eusmgms2.samsung.com (unknown [182.198.249.180]) by eusmtrp2.samsung.com (KnoxPortal) with ESMTP id 20181123153936eusmtrp24b9fb35274273b7981fcfec60ef5fc7d~pywaqKHop3195431954eusmtrp2P; Fri, 23 Nov 2018 15:39:36 +0000 (GMT) X-AuditID: cbfec7f2-5e3ff70000001159-8f-5bf81f390e3d Received: from eusmtip2.samsung.com ( [203.254.199.222]) by eusmgms2.samsung.com (EUCPMTA) with SMTP id 6C.CA.04128.83F18FB5; Fri, 23 Nov 2018 15:39:36 +0000 (GMT) Received: from imaximets.rnd.samsung.ru (unknown [106.109.129.180]) by eusmtip2.samsung.com (KnoxPortal) with ESMTPA id 20181123153936eusmtip20c127df0add6c09d58ab5a614a972bed~pywZ81IaD1843018430eusmtip2C; Fri, 23 Nov 2018 15:39:36 +0000 (GMT) From: Ilya Maximets <i.maximets@samsung.com> To: dev@dpdk.org, David Marchand <david.marchand@redhat.com> Cc: Maxime Coquelin <maxime.coquelin@redhat.com>, 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>, Ilya Maximets <i.maximets@samsung.com> Date: Fri, 23 Nov 2018 18:39:18 +0300 Message-Id: <20181123153920.12398-1-i.maximets@samsung.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20181123143620.10480-1-i.maximets@samsung.com> X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42LZduznOV1L+R/RBseaRSxurLK32L6ii83i 3aftTBZ39p5mt7jS/pPdYuPDs6wWaw99YLc41rmHxeLTgxMsFlsb/jNZbL44icmB2+PXgqWs Hov3vGTyOHZzGrvH+31X2Tz6tqxiDGCN4rJJSc3JLEst0rdL4Mo4PLGHreA1W8X6K3/YGxjX sXYxcnJICJhIbN98nxnEFhJYwShxZUloFyMXkP2FUeLmjKVsEM5nRonDM3qYYDrW3Glmh0gs Z5TonNvJBOH8YJT4tm0yG0gVm4COxKnVRxi7GDk4RARsJK5/KgKpYRZ4zySx/81fsN3CAloS d7+fZwexWQRUJd78aAPr5RWwlvjSMIkZYpu8xOoNB8BsTqA50y8+BjtJQqCbXeLAgvNQRS4S bR1P2SBsYYlXx7ewQ9gyEv93zoc6u17ifstLRojmDkaJ6Yf+QSXsJba8PscOcimzgKbE+l36 EGFHiUUvQHo5gGw+iRtvBUHCzEDmpG3TmSHCvBIdbUIQ1SoSvw8uh7pGSuLmu89QF3hIzJ8+ lQUSvP2MEkdfxExglJ+FsGsBI+MqRvHU0uLc9NRiw7zUcr3ixNzi0rx0veT83E2MwFRy+t/x TzsYv15KOsQowMGoxMNrwPwjWog1say4MvcQowQHs5IIb5Pi92gh3pTEyqrUovz4otKc1OJD jNIcLErivNUMD6KFBNITS1KzU1MLUotgskwcnFINjD3XZn1wDy12mXjD5P6sLRtuuFQv6xA7 u8bkRAKz9d7dX/ilIzbsjFF0v5rvttCBt7wmWqYzZ8XUu6weXk0fKw8H6Fe9/8v1NnearN1x cecFaa1f50l2x7prLzh8T2uXYvmcKFXOU2cDN33t3T/XmDlscXX/0/sXsq70f2kJLNY4mZ+0 0UvJV4mlOCPRUIu5qDgRAIyp+eohAwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsVy+t/xe7oW8j+iDZ5fMLS4screYvuKLjaL d5+2M1nc2Xua3eJK+092i40Pz7JarD30gd3iWOceFotPD06wWGxt+M9ksfniJCYHbo9fC5ay eize85LJ49jNaewe7/ddZfPo27KKMYA1Ss+mKL+0JFUhI7+4xFYp2tDCSM/Q0kLPyMRSz9DY PNbKyFRJ384mJTUnsyy1SN8uQS/j8MQetoLXbBXrr/xhb2Bcx9rFyMkhIWAiseZOM3sXIxeH kMBSRontt2azQSSkJH78ugBVJCzx51oXG0TRN0aJmc8b2UESbAI6EqdWH2EEsUUE7CReXgSx uTiYBb4ySey9/B1skrCAlsTd7+fBGlgEVCXe/GgDi/MKWEt8aZjEDLFBXmL1hgNgNqeAjcT0 i4/BaoSAavpm9TNOYORbwMiwilEktbQ4Nz232EivODG3uDQvXS85P3cTIzC8tx37uWUHY9e7 4EOMAhyMSjy8Nxh+RAuxJpYVV+YeYpTgYFYS4W1S/B4txJuSWFmVWpQfX1Sak1p8iNEU6KiJ zFKiyfnA2MsriTc0NTS3sDQ0NzY3NrNQEuc9b1AZJSSQnliSmp2aWpBaBNPHxMEp1cB44lfm vaDVEismcSd4HGKx7FyoKrC0yqOinaFDsKJx55MNhZW8epY/Zbr5IyXnX7c/rbndcUKpfV0/ W32u86Mb0fs2ezlf3X5Guq3sLbPe74MT7fwrUiRLi5rNmpY+ebogw6vs+SuZ4yf21Vxvvbxy mn727V41oYMCrB2Gey5OLJh8r67uS54SS3FGoqEWc1FxIgAoiAnKhQIAAA== X-CMS-MailID: 20181123153936eucas1p13bfbe13fcda92de7760ac768fcab43c5 X-Msg-Generator: CA Content-Type: text/plain; charset="utf-8" X-RootMTR: 20181123153936eucas1p13bfbe13fcda92de7760ac768fcab43c5 X-EPHeader: CA CMS-TYPE: 201P X-CMS-RootMailID: 20181123153936eucas1p13bfbe13fcda92de7760ac768fcab43c5 References: <20181123143620.10480-1-i.maximets@samsung.com> <CGME20181123153936eucas1p13bfbe13fcda92de7760ac768fcab43c5@eucas1p1.samsung.com> Subject: [dpdk-dev] [PATCH v3 0/2] IOPL related fixes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Series |
IOPL related fixes
|
|
Message
Ilya Maximets
Nov. 23, 2018, 3:39 p.m. UTC
Patches primary targeted to fix OVS unit test failures with DPDK 18.11 due to following error: 'IOPL call failed - cannot use virtio PMD'. 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(-)
Comments
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? > > 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(-) >
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(-) >> > >
On 11/23/18 4:53 PM, Ilya Maximets wrote: > 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. Thanks for the clarification. In that case, we may want it in v18.11 LTS, but I think it can wait or v18.11.1. Once in the next-virtio tree, I'll send it to stable@dpdk.org. Regards, Maxime > 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(-) >>> >> >>
On 11/23/2018 04:25 PM, Maxime Coquelin wrote: > > > On 11/23/18 4:53 PM, Ilya Maximets wrote: >> 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. > > Thanks for the clarification. > In that case, we may want it in v18.11 LTS, but I think it can wait or > v18.11.1. > It would be better if it can be in 18.11. Upstream OVS will point at a release tarball, and at present an 18.11.1 release is not due until mid-January. If it's too late for 18.11, alternatively we could do an earlier 18.11.1 release. > Once in the next-virtio tree, I'll send it to stable@dpdk.org. > > Regards, > Maxime > >> 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(-) >>>> >>> >>>
23/11/2018 21:07, Kevin Traynor: > On 11/23/2018 04:25 PM, Maxime Coquelin wrote: > > > > > > On 11/23/18 4:53 PM, Ilya Maximets wrote: > >> 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. > > > > Thanks for the clarification. > > In that case, we may want it in v18.11 LTS, but I think it can wait or > > v18.11.1. > > It would be better if it can be in 18.11. Upstream OVS will point at a > release tarball, and at present an 18.11.1 release is not due until > mid-January. If it's too late for 18.11, alternatively we could do an > earlier 18.11.1 release. I won't take any risk at this stage. The memory of the headaches we had in the past with iopl is too much strong. The real change of this patch is to register the PMD even without successful iopl. I would like to be sure it won't cause any regression.
23/11/2018 23:29, Thomas Monjalon: > 23/11/2018 21:07, Kevin Traynor: > > On 11/23/2018 04:25 PM, Maxime Coquelin wrote: > > > On 11/23/18 4:53 PM, Ilya Maximets wrote: > > >> On 23.11.2018 18:41, Maxime Coquelin wrote: > > >>> 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. > > > > > > Thanks for the clarification. > > > In that case, we may want it in v18.11 LTS, but I think it can wait or > > > v18.11.1. > > > > It would be better if it can be in 18.11. Upstream OVS will point at a > > release tarball, and at present an 18.11.1 release is not due until > > mid-January. If it's too late for 18.11, alternatively we could do an > > earlier 18.11.1 release. > > I won't take any risk at this stage. > The memory of the headaches we had in the past with iopl is too much strong. > The real change of this patch is to register the PMD even without successful iopl. > I would like to be sure it won't cause any regression. After more thinking, I decide to take the risk. Take it as a gift to OVS :-) Series applied
On 11/25/2018 10:42 AM, Thomas Monjalon wrote: > 23/11/2018 23:29, Thomas Monjalon: >> 23/11/2018 21:07, Kevin Traynor: >>> On 11/23/2018 04:25 PM, Maxime Coquelin wrote: >>>> On 11/23/18 4:53 PM, Ilya Maximets wrote: >>>>> On 23.11.2018 18:41, Maxime Coquelin wrote: >>>>>> 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. >>>> >>>> Thanks for the clarification. >>>> In that case, we may want it in v18.11 LTS, but I think it can wait or >>>> v18.11.1. >>> >>> It would be better if it can be in 18.11. Upstream OVS will point at a >>> release tarball, and at present an 18.11.1 release is not due until >>> mid-January. If it's too late for 18.11, alternatively we could do an >>> earlier 18.11.1 release. >> >> I won't take any risk at this stage. >> The memory of the headaches we had in the past with iopl is too much strong. >> The real change of this patch is to register the PMD even without successful iopl. >> I would like to be sure it won't cause any regression. > > After more thinking, I decide to take the risk. > Take it as a gift to OVS :-) > ok, thanks :-) If there's any subsequent changes needed, I will get them on an 18.11 stable branch straight away. > Series applied > >
On Sun, Nov 25, 2018 at 11:42 AM Thomas Monjalon <thomas@monjalon.net> wrote: > 23/11/2018 23:29, Thomas Monjalon: > > 23/11/2018 21:07, Kevin Traynor: > > > On 11/23/2018 04:25 PM, Maxime Coquelin wrote: > > > > On 11/23/18 4:53 PM, Ilya Maximets wrote: > > > >> On 23.11.2018 18:41, Maxime Coquelin wrote: > > > >>> 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. > > > > > > > > Thanks for the clarification. > > > > In that case, we may want it in v18.11 LTS, but I think it can wait > or > > > > v18.11.1. > > > > > > It would be better if it can be in 18.11. Upstream OVS will point at a > > > release tarball, and at present an 18.11.1 release is not due until > > > mid-January. If it's too late for 18.11, alternatively we could do an > > > earlier 18.11.1 release. > > > > I won't take any risk at this stage. > > The memory of the headaches we had in the past with iopl is too much > strong. > > The real change of this patch is to register the PMD even without > successful iopl. > > I would like to be sure it won't cause any regression. > > After more thinking, I decide to take the risk. > Take it as a gift to OVS :-) > Just for the record, this log is visible by default since 18.02 with commit: 0062818856c3 ("net/virtio: implement dynamic logging") So probably worth backporting in 18.08 at least.