From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A46ADA04F5;
	Thu, 12 Dec 2019 05:23:32 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 31795374C;
	Thu, 12 Dec 2019 05:23:32 +0100 (CET)
Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com
 [209.85.167.50]) by dpdk.org (Postfix) with ESMTP id 0170A2BC8
 for <dev@dpdk.org>; Thu, 12 Dec 2019 05:23:30 +0100 (CET)
Received: by mail-lf1-f50.google.com with SMTP id n12so591713lfe.3
 for <dev@dpdk.org>; Wed, 11 Dec 2019 20:23:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google;
 h=mime-version:from:date:message-id:subject:to;
 bh=UrB1VqJEjUz5tcWnmJXzoAyzrXPI5QEABTc7+7+5aqY=;
 b=TTxbNwRewW51Hq0K998kNqGTnZpxsia0mm5cz+bSfr1tSJavdjs3+Bjwpbt6xY9ANE
 2fLAZgmSGon/ZvAStopyJey7ZyhX8pOYVPgCwuIq5JtsmhaRcEXMnZQ4DZdxFmhktQAh
 ITmgm4Yf4pspwW4T9tpaendMePE0UOR54AZ7o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=UrB1VqJEjUz5tcWnmJXzoAyzrXPI5QEABTc7+7+5aqY=;
 b=Z+PPpwKy599lUed2qp6pkY8U1xB37fCaRLHJZiww4rjyET4CXMsUgLiM7S56om2Ba0
 GXQH3NFhaCMvT4qJTFeYlE/aTvNySXMImKEgNlLfXwJ0u6yQMiTILNkTD31tgWwex0Ms
 RKvbRRT1hrJRO6iH0CRB5jp7IERl/tjcoqoaC7msfN4YFMKSwOu8ObCfKJ+2wLrERxxk
 dxNmUZfvVmjnJZ4Qv94Ez1QHrwLT82KxMBflt3C/GC0DM8PiPvUyk+/kntCWxhwY3/f3
 IpXNMNaNXTh0flMQymHqbeH5aUH4Nmuhe5pOvD0Tpi3Zy+Rn6OqPQOgyTCWR1e9B9yk3
 +2rg==
X-Gm-Message-State: APjAAAUCEjlfEDFhb4II5WHC158evHn+gSoKC9F9USmR6hV7RlOxI8Lk
 pZU08Bq0xmP9tEjQJc25pDsH6A9Nv4LhjiEAtgXsNBTTH44=
X-Google-Smtp-Source: APXvYqxOC4tzFUJo2yfn3k6OnFgmVcp+Qdgb3uNsr2CoILSZgNJ3S6F1qjEv/Ypn51sGldNDA5aq+n/z8O7Hc304u68=
X-Received: by 2002:ac2:5a48:: with SMTP id r8mr4218081lfn.179.1576124610248; 
 Wed, 11 Dec 2019 20:23:30 -0800 (PST)
MIME-Version: 1.0
From: Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com>
Date: Thu, 12 Dec 2019 09:53:18 +0530
Message-ID: <CAJr_i82cGkKFYWEaFBTewZ2PGoKjyJajWOUhf=TNVCz6i7_1Tg@mail.gmail.com>
To: dev <dev@dpdk.org>, Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>, 
 Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev]  Question regarding device reset handling with igb_uio
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>

Hi,

    I have a question related to igb_uio.
(I have also opened a bug for this https://bugs.dpdk.org/show_bug.cgi?id=361
).

>From the below function call traces, vfio-pci module frees/allocates msi-x
vector table as part of
interrupt disable/enable. Where as igb-uio module, only masks/unmasks the
msi-x interrupt.
Does this mean, when using igb_uio, device can't undergo reset which clears
MSI-X vector table?
How to handle device reset with igb_uio?

igb-uio:
rte_intr_disable->uio_intr_disable->igbuio_pci_irqcontrol->pci_msi_mask_irq
rte_intr_enable->uio_intr_enable->igbuio_pci_irqcontrol->pci_msi_unmask_irq

igbuio_pci_open->igbuio_pci_enable_interrupts->pci_alloc_irq_vectors/request_irq
igbuio_pci_release->igbuio_pci_disable_interrupts->free_irq->pci_free_irq_vectors

vfio-pci:
rte_intr_disable->vfio_disable_msix->vfio_pci_ioctl->vfio_msi_disable->pci_free_irq_vectors
rte_intr_enable->vfio_enable_msix->vfio_pci_ioctl->vfio_msi_enable->pci_alloc_irq_vectors/vfio_msi_set_vector_signal->request_irq

Regards
-Santosh