From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Tiwei Bie <tiwei.bie@intel.com>, Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Parav Pandit <parav@mellanox.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
davem@davemloft.net, gregkh@linuxfoundation.org,
Dave Ertman <david.m.ertman@intel.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
nhorman@redhat.com, sassmann@redhat.com,
Kiran Patil <kiran.patil@intel.com>
Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus
Date: Sun, 24 Nov 2019 06:00:23 -0500 [thread overview]
Message-ID: <20191124055343-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191123230948.GF7448@ziepe.ca>
On Sat, Nov 23, 2019 at 07:09:48PM -0400, Jason Gunthorpe wrote:
> > > > > Further, I do not think it is wise to design the userspace ABI around
> > > > > a simplistict implementation that can't do BAR assignment,
> > > >
> > > > Again, the vhost-mdev follow the VFIO ABI, no new ABI is invented, and
> > > > mmap() was kept their for mapping device regions.
> > >
> > > The patches have a new file in include/uapi.
> >
> > I guess you didn't look at the code. Just to clarify, there is no
> > new file introduced in include/uapi. Only small vhost extensions to
> > the existing vhost uapi are involved in vhost-mdev.
>
> You know, I review alot of patches every week, and sometimes I make
> mistakes, but not this time. From the ICF cover letter:
>
> https://lkml.org/lkml/2019/11/7/62
>
> drivers/vfio/mdev/mdev_core.c | 21 ++
> drivers/vhost/Kconfig | 12 +
> drivers/vhost/Makefile | 3 +
> drivers/vhost/mdev.c | 556 +++++++++++++++++++++++++++++++
> include/linux/mdev.h | 5 +
> include/uapi/linux/vhost.h | 21 ++
> include/uapi/linux/vhost_types.h | 8 +
> ^^^^^^^^^^^^^^
>
> Perhaps you thought I ment ICF was adding uapi? My remarks cover all
> three of the series involved here.
Tiwei seems to be right - include/uapi/linux/vhost.h and
include/uapi/linux/vhost_types.h are both existing files. vhost uapi
extensions included here are very modest. They
just add virtio spec things that vhost was missing.
Are you looking at a very old linux tree maybe?
vhost_types.h appeared around 4.20.
--
MST
next prev parent reply other threads:[~2019-11-24 11:00 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 22:33 [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus Jeff Kirsher
2019-11-15 23:25 ` Parav Pandit
2019-11-19 3:58 ` Ertman, David M
2019-11-19 4:31 ` Parav Pandit
2019-11-19 4:39 ` Parav Pandit
2019-11-19 17:46 ` Ertman, David M
2019-11-19 18:39 ` Jason Gunthorpe
2019-11-19 17:44 ` Ertman, David M
2019-11-19 4:08 ` Jason Wang
2019-11-19 4:36 ` Parav Pandit
2019-11-19 6:51 ` Jason Wang
2019-11-19 7:13 ` Parav Pandit
2019-11-19 7:37 ` Jason Wang
2019-11-19 15:14 ` Parav Pandit
2019-11-20 3:15 ` Jason Wang
2019-11-20 3:38 ` Parav Pandit
2019-11-20 4:07 ` Jason Wang
2019-11-20 13:41 ` Jason Gunthorpe
2019-11-21 4:06 ` Jason Wang
2019-11-20 8:52 ` Michael S. Tsirkin
2019-11-20 12:03 ` Jiri Pirko
2019-11-19 16:46 ` Jason Gunthorpe
2019-11-19 18:58 ` Michael S. Tsirkin
2019-11-19 19:03 ` Jason Gunthorpe
2019-11-19 21:34 ` Michael S. Tsirkin
2019-11-19 19:15 ` Jason Gunthorpe
2019-11-19 21:33 ` Michael S. Tsirkin
2019-11-19 23:10 ` Jason Gunthorpe
2019-11-20 0:16 ` Michael S. Tsirkin
2019-11-20 1:46 ` Jason Gunthorpe
2019-11-20 3:59 ` Jason Wang
2019-11-20 5:34 ` Jason Wang
2019-11-20 13:38 ` Jason Gunthorpe
2019-11-20 14:15 ` Michael S. Tsirkin
2019-11-20 17:28 ` Alex Williamson
2019-11-20 18:11 ` Jason Gunthorpe
2019-11-20 22:07 ` Alex Williamson
2019-11-20 22:39 ` Parav Pandit
2019-11-21 8:17 ` Jason Wang
2019-11-21 3:03 ` Jason Gunthorpe
2019-11-21 4:24 ` Michael S. Tsirkin
2019-11-21 13:44 ` Jason Gunthorpe
2019-11-23 16:50 ` Michael S. Tsirkin
2019-11-21 7:21 ` Jason Wang
2019-11-21 14:17 ` Jason Gunthorpe
2019-11-22 8:45 ` Jason Wang
2019-11-22 18:02 ` Jason Gunthorpe
2019-11-23 4:39 ` Tiwei Bie
2019-11-23 23:09 ` Jason Gunthorpe
2019-11-24 11:00 ` Michael S. Tsirkin [this message]
2019-11-24 14:56 ` Tiwei Bie
2019-11-25 0:07 ` Jason Gunthorpe
2019-11-24 14:51 ` Tiwei Bie
2019-11-24 15:07 ` Michael S. Tsirkin
2019-11-25 0:09 ` Jason Gunthorpe
2019-11-25 12:59 ` Jason Wang
2019-11-23 16:48 ` Michael S. Tsirkin
2019-11-21 5:22 ` Jason Wang
2019-11-21 6:59 ` Jason Wang
2019-11-21 3:52 ` Jason Wang
2019-11-20 7:38 ` Michael S. Tsirkin
2019-11-20 13:03 ` Jason Gunthorpe
2019-11-20 13:43 ` Michael S. Tsirkin
2019-11-20 14:30 ` Jason Gunthorpe
2019-11-20 14:57 ` Michael S. Tsirkin
2019-11-20 16:45 ` Jason Gunthorpe
2019-11-20 22:05 ` Michael S. Tsirkin
2019-11-21 1:38 ` Jason Gunthorpe
2019-11-21 4:53 ` Jason Wang
2019-11-20 3:29 ` Jason Wang
2019-11-20 3:24 ` Jason Wang
2019-11-20 13:33 ` Jason Gunthorpe
2019-11-21 3:57 ` Jason Wang
2019-11-21 15:10 ` Martin Habets
2019-11-22 9:13 ` Jason Wang
2019-11-22 16:19 ` Parav Pandit
2019-11-26 12:26 ` Martin Habets
2019-11-27 10:58 ` Jason Wang
2019-11-27 11:03 ` Jason Wang
2019-11-15 23:42 ` Parav Pandit
2019-11-18 7:48 ` Greg KH
2019-11-18 22:57 ` Ertman, David M
2019-11-19 8:04 ` Jason Wang
2019-11-19 17:50 ` Ertman, David M
2019-11-18 7:49 ` Greg KH
2019-11-18 22:55 ` Ertman, David M
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=20191124055343-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jgg@ziepe.ca \
--cc=kiran.patil@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=parav@mellanox.com \
--cc=sassmann@redhat.com \
--cc=tiwei.bie@intel.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.