From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com
 [74.125.82.177]) by dpdk.org (Postfix) with ESMTP id D89D4594F
 for <dev@dpdk.org>; Thu, 22 May 2014 14:48:53 +0200 (CEST)
Received: by mail-we0-f177.google.com with SMTP id x48so3317417wes.22
 for <dev@dpdk.org>; Thu, 22 May 2014 05:49: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:date:from:to:cc:subject:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=KvgCqVsbo+654eRJGPCxzXafurIf0c0aRcrW8HARMr0=;
 b=JYub8g2gtTx4qL3topN0gqoLquv+kCpg02AGYokidG0FHzBV0szPH9qOUTnSo5iOlx
 /DM7v6+sv4LPLjM8GLplvM5Geuuw/o7p6oRh0P3VQBRBzkyAEYG+rtTQ3NOhYN0XlOUo
 Hc88FPDvNB+EomF1DxgML1imqYLLuzowk/vmYKDiRaZm8xg3Gg5eBeK8coRfmSOJBW1T
 JPmx7TceqzgTyotD7swH1VFpImRFq90ZvzCVlA1nzHobyRfG5cq7hkxP4jPUudHB9fs1
 TToDssm/nY/pNuUFwRw1s8rs44yHc9YDjo0QKN6d9sGYm0wiOz1wfY1twNHvt3/KCd+o
 uxKg==
X-Gm-Message-State: ALoCoQnvTVeHn5chvEaBB8mlnqtWs7leEOHGnkcMvEHepdbtyCWyrXSaAKH9RRO13KtYINYyfWY6
X-Received: by 10.180.36.212 with SMTP id s20mr16450232wij.18.1400762943477;
 Thu, 22 May 2014 05:49:03 -0700 (PDT)
Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.180.237])
 by mx.google.com with ESMTPSA id fu10sm7832114wib.11.2014.05.22.05.49.02
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 22 May 2014 05:49:02 -0700 (PDT)
Date: Thu, 22 May 2014 05:49:02 -0700 (PDT)
X-Google-Original-Date: Thu, 22 May 2014 14:49 +0200
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Message-ID: <13733877.G9DNOXLJDv@xps13>
Organization: 6WIND
User-Agent: KMail/4.13 (Linux/3.14.4-1-ARCH; KDE/4.13.0; x86_64; ; )
In-Reply-To: <C6ECDF3AB251BE4894318F4E451236976CC851B3@IRSMSX101.ger.corp.intel.com>
References: <C6ECDF3AB251BE4894318F4E45123697592AA9BE@IRSMSX101.ger.corp.intel.com>
 <4002874.rX8l5tMzHC@xps13>
 <C6ECDF3AB251BE4894318F4E451236976CC851B3@IRSMSX101.ger.corp.intel.com>
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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 12:48:54 -0000

2014-05-22 12:45, Burakov, Anatoly:
> > In case VFIO is backported on older kernel, it would be better to check a
> > related macro instead of Linux version.
> 
> Not sure I follow. What is the "related macro" you're referring to?

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.

-- 
Thomas