From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id C29DCAFCE for ; Tue, 27 May 2014 16:38:00 +0200 (CEST) Received: by mail-wg0-f50.google.com with SMTP id x12so9819838wgg.9 for ; Tue, 27 May 2014 07:38:11 -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=gp5JuvmgOZ13uue/3z9VdcIha17hPWDzjcsej7wK9aU=; b=kdwUM5HG/XDFKz/kThbBgs9DLY/iJF/TrxHQfkr4ShlNHva69Q5jM/iaUZlZ2xWSRK fIA4KK8yLQueppFM4qU6whTTibfK+vKzLOCvG7nPKyJe9G2kEBHTEETxkQgKCww7z6TU pE/RwMBOU/zeVCMBbM/5DM9F7FslUkmBZ0PLlFoPTqIfatOX/5XfRCxFUvKPA5MfPlPq Tznc2J/bIyjI5VYuMtTme5OLITnJVJwBsNNalajF0RRhAbV+jZvZoFIM1AdwPHU8s6cm +HWXZ4y+Nn0gL7Opi08M2AyfjQ3AdgBuGUQykwpSZewuSocne8IdnnlIjy0WHGqut4BT tdJQ== X-Gm-Message-State: ALoCoQnWLJ5oFWrd+C7MKL8VUlanMwqWkIr78mcqdqt1RdmymDsOBpXebNvJQwb+l0pnjk3EUNEK X-Received: by 10.180.126.8 with SMTP id mu8mr39002885wib.10.1401201490048; Tue, 27 May 2014 07:38:10 -0700 (PDT) Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.180.237]) by mx.google.com with ESMTPSA id ej2sm35479410wjd.21.2014.05.27.07.38.08 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 May 2014 07:38:09 -0700 (PDT) From: Thomas Monjalon To: "Burakov, Anatoly" Date: Tue, 27 May 2014 16:38:05 +0200 Message-ID: <1481821.surW3tcQHd@xps13> Organization: 6WIND User-Agent: KMail/4.13 (Linux/3.14.4-1-ARCH; KDE/4.13.0; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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:38:01 -0000 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? -- Thomas