From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by dpdk.org (Postfix) with ESMTP id 43747AFD1 for ; Tue, 27 May 2014 16:40:14 +0200 (CEST) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 27 May 2014 07:40:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,919,1392192000"; d="scan'208";a="437360569" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by azsmga001.ch.intel.com with ESMTP; 27 May 2014 07:40:13 -0700 Received: from irsmsx108.ger.corp.intel.com (163.33.3.3) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 27 May 2014 15:40:04 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.245]) by IRSMSX108.ger.corp.intel.com ([169.254.11.179]) with mapi id 14.03.0123.003; Tue, 27 May 2014 15:40:04 +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///FDAIAAEelAgAf10hD///JlgIAAEOCw Date: Tue, 27 May 2014 14:40:04 +0000 Message-ID: References: <1481821.surW3tcQHd@xps13> In-Reply-To: <1481821.surW3tcQHd@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 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: Tue, 27 May 2014 14:40:15 -0000 Hi Thomas, > 2014-05-27 14:29, Burakov, Anatoly: > > > > 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 che= cking > kernel version. > > > > > > Not sure VFIO defines any macros anywhere, but I'll look into it, tha= nks. > > > > There probably isn't. At least I don't see anything in commit log. So > > unless there's a way to get config options from kernel at compile-time > > in userspace code, I don't think we can do anything else than kernel > > version check. >=20 > Isn't it sufficient to check VFIO_API_VERSION? I believe you have to #include before you can get that macro= . The header file isn't present on kernels earlier than 3.6. Best regards, Anatoly Burakov DPDK SW Engineer