From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by dpdk.org (Postfix) with ESMTP id 15E445907 for ; Thu, 22 May 2014 15:50:53 +0200 (CEST) Received: by mail-we0-f174.google.com with SMTP id k48so3473627wev.19 for ; Thu, 22 May 2014 06:51:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=FXT7wbE5XALInc35sCEjIhhoEg9WUabw+UyT5p/Isx8=; b=mA61LOLZFyy+fpRVlq/8iEmFU/mCtW31/H8w44xpifTxzNS9RFeXLn0RUl4kZbY+1W iRjOegxnrPguDb/xuNLPLofis+EBuyKMWBSsFDN45QclNeNfIQnkxNknNPAuYMROwtlm /8QxLQ+DbRDOE6UDg451fwnVE1Jojhgot25jb7l6lHQ1AqthaNgFfF5cSXShqtBfx4IU 94beK7JUTLHZH1GLMi5YnD3p65TeixPmQNiFRrcpWgcqcefygqAzYzCM5noQL+qVd3Lf Zp5Xzq4wP6dmsIzgNHLTjnpXqXzQkgOsQkr5vfQZjw/OowPE0hYSP9PYapS6+PrcdobN 2Jhg== X-Gm-Message-State: ALoCoQkpZbxoClsFCTiDU9SpCN+iHSAMY/mCvEoBucpuyteBq/vnK2bNy7a5mdBVy5moD72aCxIE X-Received: by 10.194.19.161 with SMTP id g1mr49595289wje.20.1400766663708; Thu, 22 May 2014 06:51:03 -0700 (PDT) Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.180.237]) by mx.google.com with ESMTPSA id gi8sm487595wib.8.2014.05.22.06.51.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 May 2014 06:51:02 -0700 (PDT) From: Thomas Monjalon To: Stephen Hemminger Date: Thu, 22 May 2014 15:50:58 +0200 Message-ID: <19189491.dUSBC7Ojvo@xps13> Organization: 6WIND User-Agent: KMail/4.13 (Linux/3.14.4-1-ARCH; KDE/4.13.0; x86_64; ; ) In-Reply-To: <20140514163510.727992614@networkplumber.org> References: <20140514163401.079384157@networkplumber.org> <20140514163510.727992614@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org, Stephen Hemminger Subject: Re: [dpdk-dev] [PATCH 4/5] igb_uio: fix IRQ mode handling 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: Thu, 22 May 2014 13:50:54 -0000 Hi Stephen, 2014-05-14 09:34, Stephen Hemminger: > The igb_uio driver does not handle interrupt mode correctly. > It doesn't do the right thing and start with the most desired > mode and fall back to legacy modes as needed. I'm not sure to understand what you describe. > It also has a custom pci config lock was broken for any recent kernels. > Instead pci_intx functions that provide the needed access. I think some words are missing here. > VMWare PCI emulation of interrupts is particularly broken. > E1000 on VMWare doesn't work at all because INTX support > in ESX doesn't really work. The kernel pci_intx routines check > this and detect the failure. To handle this case fallback > to an even more legacy mode using irq enable/disable. Is it possible to split this patch for each issue? Thanks -- Thomas