From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 0857A6882 for ; Thu, 22 May 2014 14:54:40 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 22 May 2014 05:54:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,887,1392192000"; d="scan'208";a="536013301" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga001.fm.intel.com with ESMTP; 22 May 2014 05:54:49 -0700 Received: from irsmsx107.ger.corp.intel.com (163.33.3.99) by IRSMSX102.ger.corp.intel.com (163.33.3.155) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 22 May 2014 13:54:03 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.249]) by IRSMSX107.ger.corp.intel.com ([169.254.10.172]) with mapi id 14.03.0123.003; Thu, 22 May 2014 13:54:03 +0100 From: "Burakov, Anatoly" To: Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v2 07/16] Add support for VFIO interrupts, add VFIO header Thread-Index: AQHPc3pkDKAc+1Is0Ue2Bw208Qig/JtLJdiAgAFplhD///FDAIAAEelA Date: Thu, 22 May 2014 12:54:02 +0000 Message-ID: References: <4002874.rX8l5tMzHC@xps13> <13733877.G9DNOXLJDv@xps13> In-Reply-To: <13733877.G9DNOXLJDv@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 22 May 2014 14:55:48 +0200 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2 07/16] Add support for VFIO interrupts, add VFIO header 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 12:54:41 -0000 Hi Thomas, > I don't know if there is something defined in a Linux header which could = help > to check if VFIO is supported. But in general, it's better to check for a= macro > belonging to the feature instead of checking kernel version. Not sure VFIO defines any macros anywhere, but I'll look into it, thanks. Best regards, Anatoly Burakov DPDK SW Engineer