From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <liranl@nvidia.com>,
<oren@nvidia.com>, <tzahio@nvidia.com>, <leonro@nvidia.com>,
<yarong@nvidia.com>, <aviadye@nvidia.com>, <shahafs@nvidia.com>,
<artemp@nvidia.com>, <kwankhede@nvidia.com>, <ACurrid@nvidia.com>,
<gmataev@nvidia.com>, <cjia@nvidia.com>
Subject: Re: [PATCH RFC v1 0/3] Introduce vfio-pci-core subsystem
Date: Tue, 26 Jan 2021 13:23:54 -0400 [thread overview]
Message-ID: <20210126172354.GH4147@nvidia.com> (raw)
In-Reply-To: <20210125203429.587c20fd@x1.home.shazbot.org>
On Mon, Jan 25, 2021 at 08:34:29PM -0700, Alex Williamson wrote:
> > someting like this was already tried in May and didn't go anywhere -
> > are you surprised that we are reluctant to commit alot of resources
> > doing a complete job just to have it go nowhere again?
>
> That's not really what I'm getting from your feedback, indicating
> vfio-pci is essentially done, the mlx stub driver should be enough to
> see the direction, and additional concerns can be handled with TODO
> comments.
I think we are looking at this RFC in different ways. I see it as
largely "done" showing the general design of few big ideas:
- new vfio drivers will be creating treating VFIO PCI as a "VFIO bus
driver" library
- These new drivers are PCI devices bound via driver core as peers to
vfio-pci, vs sub drivers of vfio-pci
- It uses the subsystem -> driver -> library pattern for composing drivers
instead of the subsystem -> midlayer -> driver pattern mdev/platform use
- It will have some driver facing API from vfio-pci-core that is
close to what is shown in the RFC
- The drivers can "double bind" in the driver core to access the PF
resources via aux devices from the VF VFIO driver.
The point of a RFC discussion is to try to come to some community
understanding on a general high level direction.
It is not a perfectly polished illustration of things that shouldn't
be contentious or technically hard. There are alot of things that can
be polished here, this illustration has lots of stuff in vfio-pci-core
that really should be in vfio-pci - it will take time and effort to
properly split things up and do a great job here.
> Sorry if this is not construed as actual feedback, I think both
> Connie and I are making an effort to understand this and being
> hampered by lack of a clear api or a vendor driver that's anything
> more than vfio-pci plus an aux bus interface. Thanks,
I appreciate the effort, and there is a lot to understand here. Most
of this stuff is very new technology and not backed by industry
standards bodies.
I really do think this simplified RFC will help the process - I've
seen the internal prototype and it is a mass of opaque device specific
code. Max's V2 should flesh things out more.
Thanks,
Jason
prev parent reply other threads:[~2021-01-26 22:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 18:15 [PATCH RFC v1 0/3] Introduce vfio-pci-core subsystem Max Gurtovoy
2021-01-17 18:15 ` [PATCH 1/3] vfio-pci: rename vfio_pci.c to vfio_pci_core.c Max Gurtovoy
2021-01-17 18:15 ` [PATCH 2/3] vfio-pci: introduce vfio_pci_core subsystem driver Max Gurtovoy
2021-01-17 18:15 ` [PATCH 3/3] mlx5-vfio-pci: add new vfio_pci driver for mlx5 devices Max Gurtovoy
2021-01-18 13:38 ` [PATCH RFC v1 0/3] Introduce vfio-pci-core subsystem Cornelia Huck
2021-01-18 15:10 ` Jason Gunthorpe
2021-01-18 16:00 ` Cornelia Huck
2021-01-18 18:16 ` Jason Gunthorpe
2021-01-19 18:56 ` Cornelia Huck
2021-01-19 19:42 ` Jason Gunthorpe
2021-01-22 19:25 ` Alex Williamson
2021-01-22 20:04 ` Jason Gunthorpe
2021-01-25 16:20 ` Cornelia Huck
2021-01-25 18:04 ` Jason Gunthorpe
2021-01-25 23:31 ` Alex Williamson
2021-01-26 0:45 ` Jason Gunthorpe
2021-01-26 3:34 ` Alex Williamson
2021-01-26 13:27 ` Max Gurtovoy
2021-01-28 16:29 ` Cornelia Huck
2021-01-28 21:02 ` Alex Williamson
2021-01-31 18:46 ` Max Gurtovoy
2021-02-01 4:32 ` Alex Williamson
2021-02-01 9:40 ` Max Gurtovoy
2021-02-01 17:29 ` Alex Williamson
2021-02-01 17:17 ` Jason Gunthorpe
2021-01-31 18:09 ` Max Gurtovoy
2021-01-26 17:23 ` Jason Gunthorpe [this message]
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=20210126172354.GH4147@nvidia.com \
--to=jgg@nvidia.com \
--cc=ACurrid@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=artemp@nvidia.com \
--cc=aviadye@nvidia.com \
--cc=cjia@nvidia.com \
--cc=cohuck@redhat.com \
--cc=gmataev@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liranl@nvidia.com \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=tzahio@nvidia.com \
--cc=yarong@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).