From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 6444DA00E6 for ; Fri, 14 Jun 2019 15:58:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 39D291D546; Fri, 14 Jun 2019 15:58:09 +0200 (CEST) Received: from mail-io1-f45.google.com (mail-io1-f45.google.com [209.85.166.45]) by dpdk.org (Postfix) with ESMTP id A9EE41D544 for ; Fri, 14 Jun 2019 15:58:08 +0200 (CEST) Received: by mail-io1-f45.google.com with SMTP id k8so6034751iot.1 for ; Fri, 14 Jun 2019 06:58:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=PL05HIWZrdYmUUiWOo6/UmoBscCmIcrMAigRM54zbds=; b=o1B6o+v213mdm3XV0v309aASbSXQWr+VJw/hiopUl30glJuNkd9lzi3K1EiJReRNyP 5NqbYOhL+3RGvHheEXOtrjyntRhJ4QpRYsY7V0/Pqs7FgJdwxhSkDn9VANTVF2/3Jvem icbwN78Q5BLUgTf83NkvL6RFy8gbq6C0etF4Rj9LQjA5S6pAOECM1ZkcZqvWhoAgDItH ku4PNTdfIHNK0h2iKVEIH9qZR9YBlVadwzblfTN019md2JsvdmfyH6dqac4u7fuF9ixt ByLp1e737yrqvjeL8ueaUogr4HjUiI/pYixXGzHuP+ycqkZXe0hn+/j/zrFuK7ci8xjD n7+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=PL05HIWZrdYmUUiWOo6/UmoBscCmIcrMAigRM54zbds=; b=RRYtvqsB/DlSAg7gjCguJKUy2AlTRK+pEost58M5R6jHjWKl5nlop+j5M3TDTxvGbC UlrPS7rNmYAon/ISHbyk9yx9s4cBaD5OKgvofHZip6z3WRAIENdE3iAYB7AC4TMD9Eos J00Sfe/B7l0uDMW5hWXvKtkdWd3SAlCvH9LEdYCTAKT6wsrrq6A9CtIyrtt9aaopRHkI 60Sof6tL00KKWXBZzYNzZK29uE4zXBhp6NBBFhbQjzHABYHfAfnawoV7iaGY2Kvm9xgh r1da2MSmmeQ3gY9qE8AW/x5c7pf95n42OEHlj57E6mzgqisPXZU9UasQlAVTP0Bzj2rD kvOA== X-Gm-Message-State: APjAAAUYVSycABLiVRv7N6W7DVCMC6uzdv9o1pFe5TztkN2xs/IebXkv GlEfXmt0a+PTC1qyiqP2D+iqQFtxCPDU2T1NiTu8eSF7 X-Google-Smtp-Source: APXvYqwHj4VBYFAtL39gzJ2rsRSXrQlQmYe6qOIE+88k2QFSLgXzwG/2XT2vnIbk43XxMav1YQ/xJQcj6phLY/KUtf0= X-Received: by 2002:a02:a001:: with SMTP id a1mr22050700jah.115.1560520687848; Fri, 14 Jun 2019 06:58:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Santosh R Date: Fri, 14 Jun 2019 19:27:52 +0530 Message-ID: To: dev@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, I have some question on igb_uio. >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