From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 07/16] Add support for VFIO interrupts, add VFIO header Date: Tue, 27 May 2014 16:46:04 +0200 Message-ID: <3757253.C786Iy0Bh3@xps13> References: <1481821.surW3tcQHd@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: "Burakov, Anatoly" Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-05-27 14:40, Burakov, Anatoly: > > 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 > > > > > checking kernel version. > > > > > > Not sure VFIO defines any macros anywhere, but I'll look into it, > > > > thanks. > > > > > > 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. > > > > 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. Oh yes, you're right :) -- Thomas