From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id ED6F2A04F2; Fri, 6 Dec 2019 17:56:03 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 28FA21BF8D; Fri, 6 Dec 2019 17:56:03 +0100 (CET) Received: from mail-pg1-f196.google.com (mail-pg1-f196.google.com [209.85.215.196]) by dpdk.org (Postfix) with ESMTP id 302E71BF8B for ; Fri, 6 Dec 2019 17:56:01 +0100 (CET) Received: by mail-pg1-f196.google.com with SMTP id a33so3377733pgm.5 for ; Fri, 06 Dec 2019 08:56:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=yHUSPs6yLFdEqs218mB9bBjorsiwaNqobV3/zvmZnY0=; b=PZ2yHBWcSnbD1R8WYygxWscDQWxqrcuclssInrfX2UVI6HrhmtYfLtUgJ2IpZzlPMK xv5Ul3UG0nMom0nde8cVJnO/OIcogix1r62MyrIrtuTBBDwsQHBlPqoqafTDhlU3LPBY E0a6xalgZtj7A8nGyG6gBCLVn2zAAAcBkXZUtdWpWnPd97YniDC2stijISupY5+IWKHX AL19r9qlpHl1hvLGuwhljFapGzxk5J9vBfuPxIeAUwsdXf5ntVjsCm8Gb4KlcaDEn2wr /6BXKmZdrG1Heinavn6smPWaXLTEDi6h3hqh9RrdoXGqcIVtgEqd/SLi0dKvlm1WDl9j jATQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=yHUSPs6yLFdEqs218mB9bBjorsiwaNqobV3/zvmZnY0=; b=Bo5Lkzcb1G6ELJFTZOpHjJS/KCBnQ+nUMrN1lBDbUNwUctO1ozHs+xDxxoqWnUEybE 1TLF+gDMadzMrjdjrsxuOr6MlWYD35V78lgLf5XODLWwjspIZSSUy4ubJ5A1o6Lu8yLz T5UuDt1glOzYnUgsGCWmGO7B/k32RNM9RM6gd0TwSaAw7UUyi7+F+Gkv7focHM2KUlGe 4OjStGZ1YevfELGNUIBs31Bc96QlQZZmZWEJ/bTqyNdnOHJBLo+73zKf4nQ9JzMbcCiU /BK07jIrezS0Z4A/yQf9NhqlYk1KcrgMW8HX9EcKOqIU8W+Ek7q9unCPoEMD8E7rrLno 4kRg== X-Gm-Message-State: APjAAAUndChySMbRFouOAMvdKCy4r51CMgBlZcymp0QtUmdASyvb7u2U XmrK1Juxuf5T178X33APKUnSUJJGY5jVMg== X-Google-Smtp-Source: APXvYqzKnpbb5dcDlR105lkeG/CF8RsybzrE8NGBZYVSSyFuYjx7kJYSv4C3hv5UahbdX6AL8unCWQ== X-Received: by 2002:a63:4c4f:: with SMTP id m15mr4530367pgl.346.1575651360032; Fri, 06 Dec 2019 08:56:00 -0800 (PST) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id c9sm16550626pfn.65.2019.12.06.08.55.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 Dec 2019 08:55:59 -0800 (PST) Date: Fri, 6 Dec 2019 08:55:50 -0800 From: Stephen Hemminger To: Ranran Cc: dev@dpdk.org Message-ID: <20191206085550.7bd4df0d@hermes.lan> In-Reply-To: References: <20191130085103.261db7ef@hermes.lan> <20191201090707.450b6a4f@hermes.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] Interrupt is catched in kernel, but not handled 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" On Sun, 1 Dec 2019 20:16:59 +0200 Ranran wrote: > =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A =D7=99=D7=95=D7=9D =D7=90=D7=B3, 1 = =D7=91=D7=93=D7=A6=D7=9E=D7=B3 2019, 19:07, =D7=9E=D7=90=D7=AA Stephen Hemm= inger =E2=80=8F< > stephen@networkplumber.org>: >=20 > > On Sat, 30 Nov 2019 19:49:16 +0200 > > Ranran wrote: > > > > > > > > > > > > I also verified that there are no additional irq numbered 23 exce= pt > > > > > for our device. > > > > > > > > > > How can it be that irq is catched, but not delivered to userspace= ? > > > > > Any suggestion is much appreciated, > > > > > > > > > > ran > > > > > > > > UIO PCI generic does not support interrupts. > > > > You need to use VFIO (preferred) or igb_uio > > > > > > > > Actually UIO PCI generic does support interrupts but only legacy INTx, > > it does not support MSI or MSI-x modes. > > >=20 > Right. > The device I work with is FPGA xilinx which should support INTx. Yet, even > though irqhandler is called, it does not pass pci_check_and_mask_intx, and > therefore irq is not handled, as I written in the original post. Your problem may be that the FPGA is not correctly implementing the PCI spe= c. I saw this before with VMWare. The kernel expects to be able to read the PCI_COMMAND register to see if IRQ is pending and then write back INTX_DISABLE bit.