From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id CD870A00C5 for ; Wed, 2 Feb 2022 16:10:59 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6DD1740689; Wed, 2 Feb 2022 16:10:59 +0100 (CET) Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) by mails.dpdk.org (Postfix) with ESMTP id 9F5F340688 for ; Wed, 2 Feb 2022 16:10:57 +0100 (CET) Received: by mail-ot1-f52.google.com with SMTP id e21-20020a9d0195000000b005a3cd7c1e09so13050129ote.6 for ; Wed, 02 Feb 2022 07:10:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=fHKaEQ2JQZFgCg6WnDFXS4V/mIA9chVymPG1d7zpC8Q=; b=p6H8NFxfDadpdrc1xsJgyQhHOzZVnr+yH4Gz4AgAAHC4xta9APWmly/jZryIhPpnSQ 4HMT7nWysbjq+lRkJoWqZGjBhV1xAkWHrhHXugt6BP5wTfva4XoZyaYsQrHauKLO10wM DLwnIf6V4upDnbdBkECFQSrK+nD5GYHBIUBeUrm7ooOdxOPZwNOwYOsDX6FtFKmuQjGC NeMtd2v2bA9TfXwbP2sryq7kn/Dpsx5T3fhmSdaDQIJu15aaweXdN7zS+kgusNC0xC08 Oh9CPfPym+NIsPaDNNrSxOuuJORmJareYKJtOhFV59pKiMmNRRWDyDC5YctUlw6rbEew apzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fHKaEQ2JQZFgCg6WnDFXS4V/mIA9chVymPG1d7zpC8Q=; b=7rCqwOsi3i3fDvQepvqnQPMlYB3NtGaA6iY5wthwW2/Xl/3T84wh2ewplv/tstR5Gr 6fgDm+7AAX3awHSkHQyOkeTEVPW87rcLOziz4YD4iruJVw/XDJgK/f/cWozNdyEQdtz1 4XlEzITsAS6dWbVB6V3nTfiGg8LEjhR8Jsm3MSkAY48cbQVIiAD9YsZAXXD4lsz6GktG PWQaTAm9Ow5a5WAV8va49eMxUHRdx30bNbWyjtcfDMM5hYaYpM3WF4Y8Wu4uDhzErZb1 DhmpO0FtcxY/1QWXVV1BIipRrpPsd5MFYv61oMQO6oYlzmpfwzQg5gHMJ7KREgcyFnxs f6mg== X-Gm-Message-State: AOAM531quemFpkQKDfIy0HurCnMo5ExI2yTEvZ6unQNg7Fh0Yr80bEr6 3nGKeVNOiAwMqeSe4nrwXgZumlniKyeludyUvFJmcPAKnoQ= X-Google-Smtp-Source: ABdhPJzz4Wk+NLIldT7NNYnRDYIKTZNccDonzd/thVQH6g+ydmlGULZIaz+vWWX6YbQt0iik1wSjXjKxxB7EgIQqG6U= X-Received: by 2002:a05:6830:4c9:: with SMTP id s9mr17690851otd.12.1643814656625; Wed, 02 Feb 2022 07:10:56 -0800 (PST) MIME-Version: 1.0 From: madhukar mythri Date: Wed, 2 Feb 2022 20:40:45 +0530 Message-ID: Subject: Issue with parsing devargs syntax on Hyper-V platforms with DPDK-21.11 To: users Content-Type: multipart/alternative; boundary="000000000000af4f3d05d70a6cca" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000af4f3d05d70a6cca Content-Type: text/plain; charset="UTF-8" Hi, On the Hyper-V(Azure) environment with/without Accelerated mode, we are seeing segmentation-fault issues while running the secondary process of DPDK with legacy syntax of arguments on DPDK-21.11 version. Whereas the same arguments were working well till the DPDK-21.08 version, only with the latest DPDK-21.11 this issue occurs. Here is the EAL argument syntax to load 'net_failsafe' PMD: --vdev net_vdev_netvsc0,iface=s1p0 --block 032e:00:02.0 As per analysis on this, found that a new feature was introduced "Enabled new devargs parser" in DPDK-21.11 version. As part of this new feature found that this DPDK patch caused this issue: https://patchwork.dpdk.org/project/dpdk/patch/1618283653-16510-6-git-send-email-xuemingl@nvidia.com/ When we remove this patch code, we do not see any issues with loading primary/secondary processes. So, looks like an issue in identifying the new global syntax and fallback to legacy syntax w.r.t to Hyper-V platforms. Even we tried to give new syntax as mentioned in this patch to load this "vdev" based bus as follows, but still seeing issues. -a bus=vdev,name=net_vdev_netvsc0/class=eth/driver=vdev_netvsc Does the new syntax support the "vdev_netvsc"(Hyper-V) based PMD ? If so, please let us know, the syntax on the same. Thanks, Madhukar. --000000000000af4f3d05d70a6cca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On the Hyper-V(Azure) environment with/without = Accelerated mode, we are seeing segmentation-fault issues while running the= secondary process of DPDK with legacy syntax of arguments on DPDK-21.11 ve= rsion.
Whereas the same arguments were working well till the DPDK-21.08 = version, only with the latest DPDK-21.11 this issue occurs.

Here is = the EAL argument syntax to load 'net_failsafe' PMD:
=C2=A0 =C2= =A0--vdev net_vdev_netvsc0,iface=3Ds1p0 --block 032e:00:02.0

As per = analysis on this, found that a new feature was introduced "Enabled new= devargs parser" in DPDK-21.11 version. As part of this new feature fo= und that this DPDK patch caused this issue:
https://patchwork.dpdk.org/project/dpdk/patch/1618283653-16510-6-= git-send-email-xuemingl@nvidia.com/

When we remove this pa= tch code, we do not see any issues with loading primary/secondary processes= . So, looks like an issue in identifying the new global syntax and fallback= to legacy syntax w.r.t to Hyper-V platforms.

Even we tried to give = new syntax as mentioned in this patch to load this "vdev" based b= us as follows, but still seeing issues.
=C2=A0 =C2=A0 =C2=A0-a bus=3Dvde= v,name=3Dnet_vdev_netvsc0/class=3Deth/driver=3Dvdev_netvsc

Does the = new syntax support the "vdev_netvsc"(Hyper-V) based PMD ? If so, = please let us know, the syntax on the same.

Thanks,
Madhukar.

--000000000000af4f3d05d70a6cca--