From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 77EE0594D for ; Tue, 20 May 2014 13:28:20 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 20 May 2014 04:28:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,873,1392192000"; d="scan'208";a="514727768" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga001.jf.intel.com with ESMTP; 20 May 2014 04:28:26 -0700 Received: from irsmsx153.ger.corp.intel.com (163.33.192.75) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 20 May 2014 12:26:35 +0100 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.98]) by IRSMSX153.ger.corp.intel.com ([169.254.9.50]) with mapi id 14.03.0123.003; Tue, 20 May 2014 12:26:34 +0100 From: "Burakov, Anatoly" To: Stephen Hemminger Thread-Topic: [PATCH v2 10/16] Added support for selecting VFIO interrupt type from EAL command-line Thread-Index: AQHPc3pWSBnVPJpZekO5ZwszQ5vuf5tJBdEAgAAeIqCAACAmgIAAETIA Date: Tue, 20 May 2014 11:26:34 +0000 Message-ID: References: <1400514709-24087-11-git-send-email-anatoly.burakov@intel.com> <20140520042323.4dbea108@samsung-9> In-Reply-To: <20140520042323.4dbea108@samsung-9> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2 10/16] Added support for selecting VFIO interrupt type from EAL command-line X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 11:28:21 -0000 Hi Stephen, > I am not sure that MSI-X has any advantage with only one IRQ, so MSI woul= d > do. Igb_uio doesn't support MSI, so I never included MSI support. It can be add= ed though, but I don't see much point. > Then have the code look at the PCI capability of device and fallback to I= NTX if > needed. It should also check if INTX works, see kernel for details, since= some > PCI emulation like VMware is broken. I believe VFIO itself does that already when it sets up interrupts. Best regards, Anatoly Burakov DPDK SW Engineer