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 BEE54A00C5 for ; Thu, 15 Sep 2022 09:23:06 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 484484021D; Thu, 15 Sep 2022 09:23:06 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id AAF6D40156 for ; Thu, 15 Sep 2022 09:23:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1663226585; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7IOOgR3iLVDo+idEZlOZ2em19AFQZsd36RMMyXPYpGI=; b=I6Mcf7D/pKgY9FDUbsdgwvZb0obQVXZ3jZdwb7mkjXT0xlvRoyX6TmdCUSVd+PaBCQKTWm 8M5wASBLPFTDeC+ueLL7ZOhYVGqfdg+V8FM7Px5IyqjyLl0CQsQhfYpCnfyzYZgtnt/QsF iCtW5YwWsXpbwPzCPPIzEOWrfEgVp8w= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-554-xbcrRk2eNxi-tvkWsedDeg-1; Thu, 15 Sep 2022 03:23:04 -0400 X-MC-Unique: xbcrRk2eNxi-tvkWsedDeg-1 Received: by mail-lj1-f200.google.com with SMTP id d20-20020a2eb054000000b0026c08f42b50so3662719ljl.20 for ; Thu, 15 Sep 2022 00:23:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=7IOOgR3iLVDo+idEZlOZ2em19AFQZsd36RMMyXPYpGI=; b=5Ew2ws0JocJh9Um3AiI+LOCsqbkr1tZT4SN+8CdY+yA9pmmuBwWnT96F0h/vjeyFNc 1yeAKFq6NktxYMRlxeXhf4pvqW7hvV6sELZ6Nq5QL42xmLvOU6UpvYUYum0BoifT0IVx kXjtH2qvdGvvsAnX0HeXgBZjqJDlv683/qLfULNv9KkWa4USNoyvcDdJOQAon+MS0O4x mPK1RQNXtyquXjOfRPnbygZAlrZFSpRt0KfuJkgr37yBzfpm6qJB4a9hZyu+AFKnujwA ISpEXJ4K/nTmRg65DcW8wI3GIhjOh3fJHrL3onQGFE5G6oZxH9cVL+kuhsIeDQobolEB 36jw== X-Gm-Message-State: ACgBeo0cXD3x+oxE6UbPyHVqBlCstM3wl5CHNu9TWVVsfpNa3OW1q1s0 RwBy1hbdB2t8C7ubC3EuWkoclbFTZJWyzOJNmE4oG+PNdr9lkvgvjTkdbjvGylK92L8C7piY5WQ J4DS6YlpQIsh/flTKUqb0Mg== X-Received: by 2002:a05:6512:32c8:b0:49a:91d7:1bbf with SMTP id f8-20020a05651232c800b0049a91d71bbfmr6133028lfg.560.1663226582699; Thu, 15 Sep 2022 00:23:02 -0700 (PDT) X-Google-Smtp-Source: AA6agR7dvPVA9PUm8FGTZo1CvYBVCz0AMk6Gd6IGY3ZD0pdHnTZ+G0o+YyF6KQf/tVk5CiCogiwCSW/xCIvi66ldt0Y= X-Received: by 2002:a05:6512:32c8:b0:49a:91d7:1bbf with SMTP id f8-20020a05651232c800b0049a91d71bbfmr6133023lfg.560.1663226582488; Thu, 15 Sep 2022 00:23:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Thu, 15 Sep 2022 09:22:51 +0200 Message-ID: Subject: Re: how to bind VF interface into dpdk To: Balakrishnan K Cc: "users@dpdk.org" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Wed, Sep 14, 2022 at 2:30 PM Balakrishnan K wrote: > > I am trying to bind VF interface to dpdk using dpdk-devbind.py. > > Unable to bind getting error =E2=80=9Ccannot bind to driver uio_pci_gener= ic=E2=80=9D. > > Steps followed: > > 1.modprobe uio_pci_generic > > 2. dpdk-devbind.py -b uio_pci_generic 0000:05:00.0 In general, you should use vfio-pci. Now, for your particular case, ixgbe VF devices (10ed) won't work with uio_pci_generic, and it is reported in the driver info. $ ./usertools/dpdk-pmdinfo.py build-gcc/drivers/librte_net_ixgbe.so | less PMD NAME: net_ixgbe_vf PMD PARAMETERS: pflink_fullchk=3D<0|1> PMD KMOD DEPENDENCIES: * igb_uio | vfio-pci PMD HW SUPPORT: Intel Corporation (8086) : 82599 Ethernet Controller Virtual Function (10ed) (All Subdevices) Intel Corporation (8086) : 82599 Virtual Function (152e) (All Subdevices) Intel Corporation (8086) : X540 Ethernet Controller Virtual Function (1515) (All Subdevices) Intel Corporation (8086) : X540 Virtual Function (1530) (All Subdevices) Intel Corporation (8086) : X550 Virtual Function (1564) (All Subdevices) Intel Corporation (8086) : X550 Virtual Function (1565) (All Subdevices) Intel Corporation (8086) : X553 Virtual Function (15c5) (All Subdevices) Intel Corporation (8086) : X553 Virtual Function (15b4) (All Subdevices) Intel Corporation (8086) : Ethernet Connection X552 Virtual Function (15a8) (All Subdevices) Intel Corporation (8086) : X552 Virtual Function (15a9) (All Subdevices) ... > > Also tried with vfio-pci driver not succeeded. We need dmesg output in this case, to be sure. In general, it means that either your system has no iommu (there is a special *unsafe* mode, for handling this case), or the iommu is not configured. Please see https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#vfio --=20 David Marchand