All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: 陈能 <chenneng@tsingmicro.com>
Cc: cohuck <cohuck@redhat.com>, kvm <kvm@vger.kernel.org>,
	"Owen.Yan" <owen.yan@tsingmicro.com>,
	程文 <chengwen@tsingmicro.com>, Terry <terry@tsingmicro.com>
Subject: Re: Clarify the functions of each version of VFIO
Date: Tue, 19 Jul 2022 08:36:10 -0600	[thread overview]
Message-ID: <20220719083610.6e009286.alex.williamson@redhat.com> (raw)
In-Reply-To: <tencent_64D724EC138B1F2238BD5AB4@qq.com>

On Tue, 19 Jul 2022 15:45:17 +0800
"陈能" <chenneng@tsingmicro.com> wrote:

> Hi Maintainers,
> &nbsp; &nbsp;&nbsp;We try to develop a user space driver based on
> VFIO, but we don't know the version of the kernel on host machine.
> Maybe it's a latest kernel(5.x) or an older kernel(3.x). However the
> kernel supports VFIO from version 3.6.And VFIO of the 5.10 kernel
> version has about 1000 lines of code more than VFIO of the 3.6 kernel
> version.we don't know the functional difference between VFIO of each
> version. For example, a driver based on the latest VFIO, can I run it
> on the older VFIO? Besides,&nbsp;Can you help provide the function
> list/release note of each version of VFIO? Thanks a lot.

You can certainly look at the commit log of the documented uAPI:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/include/uapi/linux/vfio.h

In general the uAPI is backwards compatible, there's essentially a base
set of features along with capabilities and extensions that can be
discovered.  You can look at other userspace drivers like QEMU or DPDK
which also don't specifically rely on knowing the underlying kernel
version, they make use of features and capabilities as they're
available.  Thanks,

Alex


           reply	other threads:[~2022-07-19 14:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <tencent_64D724EC138B1F2238BD5AB4@qq.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220719083610.6e009286.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=chengwen@tsingmicro.com \
    --cc=chenneng@tsingmicro.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=owen.yan@tsingmicro.com \
    --cc=terry@tsingmicro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.