From: gregkh <gregkh@linuxfoundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: alsa-devel@alsa-project.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Takashi Iwai <tiwai@suse.de>, Jason Wang <jasowang@redhat.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Leon Romanovsky <leonro@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Fred Oh <fred.oh@linux.intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
"Patil, Kiran" <kiran.patil@intel.com>,
Mark Brown <broonie@kernel.org>, Parav Pandit <parav@nvidia.com>,
David M Ertman <david.m.ertman@intel.com>,
Roi Dayan <roid@nvidia.com>,
virtualization@lists.linux-foundation.org, "Saleem,
Shiraz" <shiraz.saleem@intel.com>,
Netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH mlx5-next v1 06/11] vdpa/mlx5: Connect mlx5_vdpa to auxiliary bus
Date: Thu, 5 Nov 2020 08:33:02 +0100 [thread overview]
Message-ID: <20201105073302.GA3415673@kroah.com> (raw)
In-Reply-To: <CAPcyv4jP9nFAGdvB7agg3x7Y7moHGcxLd5=f5=5CXnJRUf3n9w@mail.gmail.com>
On Wed, Nov 04, 2020 at 03:21:23PM -0800, Dan Williams wrote:
> On Tue, Nov 3, 2020 at 7:45 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> [..]
> > > +MODULE_DEVICE_TABLE(auxiliary, mlx5v_id_table);
> > > +
> > > +static struct auxiliary_driver mlx5v_driver = {
> > > + .name = "vnet",
> > > + .probe = mlx5v_probe,
> > > + .remove = mlx5v_remove,
> > > + .id_table = mlx5v_id_table,
> > > +};
> >
> > It is hard to see from the diff, but when this patch is applied the
> > vdpa module looks like I imagined things would look with the auxiliary
> > bus. It is very similar in structure to a PCI driver with the probe()
> > function cleanly registering with its subsystem. This is what I'd like
> > to see from the new Intel RDMA driver.
> >
> > Greg, I think this patch is the best clean usage example.
> >
> > I've looked over this series and it has the right idea and
> > parts. There is definitely more that can be done to improve mlx5 in
> > this area, but this series is well scoped and cleans a good part of
> > it.
>
> Greg?
>
> I know you alluded to going your own way if the auxiliary bus patches
> did not shape up soon, but it seems they have and the stakeholders
> have reached this consensus point.
>
> Were there any additional changes you wanted to see happen? I'll go
> give the final set another once over, but David has been diligently
> fixing up all the declared major issues so I expect to find at most
> minor incremental fixups.
This is in my to-review pile, along with a load of other stuff at the
moment:
$ ~/bin/mdfrm -c ~/mail/todo/
1709 messages in /home/gregkh/mail/todo/
So give me a chance. There is no rush on my side for this given the
huge delays that have happened here on the authorship side many times in
the past :)
If you can review it, or anyone else, that is always most appreciated.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh <gregkh@linuxfoundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
Jason Wang <jasowang@redhat.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Netdev <netdev@vger.kernel.org>, Parav Pandit <parav@nvidia.com>,
Roi Dayan <roid@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>,
virtualization@lists.linux-foundation.org,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Mark Brown <broonie@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Fred Oh <fred.oh@linux.intel.com>,
"Saleem, Shiraz" <shiraz.saleem@intel.com>,
"Patil, Kiran" <kiran.patil@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David M Ertman <david.m.ertman@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH mlx5-next v1 06/11] vdpa/mlx5: Connect mlx5_vdpa to auxiliary bus
Date: Thu, 5 Nov 2020 08:33:02 +0100 [thread overview]
Message-ID: <20201105073302.GA3415673@kroah.com> (raw)
In-Reply-To: <CAPcyv4jP9nFAGdvB7agg3x7Y7moHGcxLd5=f5=5CXnJRUf3n9w@mail.gmail.com>
On Wed, Nov 04, 2020 at 03:21:23PM -0800, Dan Williams wrote:
> On Tue, Nov 3, 2020 at 7:45 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> [..]
> > > +MODULE_DEVICE_TABLE(auxiliary, mlx5v_id_table);
> > > +
> > > +static struct auxiliary_driver mlx5v_driver = {
> > > + .name = "vnet",
> > > + .probe = mlx5v_probe,
> > > + .remove = mlx5v_remove,
> > > + .id_table = mlx5v_id_table,
> > > +};
> >
> > It is hard to see from the diff, but when this patch is applied the
> > vdpa module looks like I imagined things would look with the auxiliary
> > bus. It is very similar in structure to a PCI driver with the probe()
> > function cleanly registering with its subsystem. This is what I'd like
> > to see from the new Intel RDMA driver.
> >
> > Greg, I think this patch is the best clean usage example.
> >
> > I've looked over this series and it has the right idea and
> > parts. There is definitely more that can be done to improve mlx5 in
> > this area, but this series is well scoped and cleans a good part of
> > it.
>
> Greg?
>
> I know you alluded to going your own way if the auxiliary bus patches
> did not shape up soon, but it seems they have and the stakeholders
> have reached this consensus point.
>
> Were there any additional changes you wanted to see happen? I'll go
> give the final set another once over, but David has been diligently
> fixing up all the declared major issues so I expect to find at most
> minor incremental fixups.
This is in my to-review pile, along with a load of other stuff at the
moment:
$ ~/bin/mdfrm -c ~/mail/todo/
1709 messages in /home/gregkh/mail/todo/
So give me a chance. There is no rush on my side for this given the
huge delays that have happened here on the authorship side many times in
the past :)
If you can review it, or anyone else, that is always most appreciated.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh <gregkh@linuxfoundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: alsa-devel@alsa-project.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Takashi Iwai <tiwai@suse.de>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Leon Romanovsky <leonro@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Fred Oh <fred.oh@linux.intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
"Patil, Kiran" <kiran.patil@intel.com>,
Mark Brown <broonie@kernel.org>, Parav Pandit <parav@nvidia.com>,
David M Ertman <david.m.ertman@intel.com>,
Roi Dayan <roid@nvidia.com>,
virtualization@lists.linux-foundation.org, "Saleem,
Shiraz" <shiraz.saleem@intel.com>,
Netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH mlx5-next v1 06/11] vdpa/mlx5: Connect mlx5_vdpa to auxiliary bus
Date: Thu, 5 Nov 2020 08:33:02 +0100 [thread overview]
Message-ID: <20201105073302.GA3415673@kroah.com> (raw)
In-Reply-To: <CAPcyv4jP9nFAGdvB7agg3x7Y7moHGcxLd5=f5=5CXnJRUf3n9w@mail.gmail.com>
On Wed, Nov 04, 2020 at 03:21:23PM -0800, Dan Williams wrote:
> On Tue, Nov 3, 2020 at 7:45 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> [..]
> > > +MODULE_DEVICE_TABLE(auxiliary, mlx5v_id_table);
> > > +
> > > +static struct auxiliary_driver mlx5v_driver = {
> > > + .name = "vnet",
> > > + .probe = mlx5v_probe,
> > > + .remove = mlx5v_remove,
> > > + .id_table = mlx5v_id_table,
> > > +};
> >
> > It is hard to see from the diff, but when this patch is applied the
> > vdpa module looks like I imagined things would look with the auxiliary
> > bus. It is very similar in structure to a PCI driver with the probe()
> > function cleanly registering with its subsystem. This is what I'd like
> > to see from the new Intel RDMA driver.
> >
> > Greg, I think this patch is the best clean usage example.
> >
> > I've looked over this series and it has the right idea and
> > parts. There is definitely more that can be done to improve mlx5 in
> > this area, but this series is well scoped and cleans a good part of
> > it.
>
> Greg?
>
> I know you alluded to going your own way if the auxiliary bus patches
> did not shape up soon, but it seems they have and the stakeholders
> have reached this consensus point.
>
> Were there any additional changes you wanted to see happen? I'll go
> give the final set another once over, but David has been diligently
> fixing up all the declared major issues so I expect to find at most
> minor incremental fixups.
This is in my to-review pile, along with a load of other stuff at the
moment:
$ ~/bin/mdfrm -c ~/mail/todo/
1709 messages in /home/gregkh/mail/todo/
So give me a chance. There is no rush on my side for this given the
huge delays that have happened here on the authorship side many times in
the past :)
If you can review it, or anyone else, that is always most appreciated.
thanks,
greg k-h
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2020-11-05 7:33 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 20:15 [PATCH mlx5-next v1 00/11] Convert mlx5 to use auxiliary bus Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 01/11] net/mlx5: Don't skip vport check Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 02/11] net/mlx5: Properly convey driver version to firmware Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-02 14:47 ` Roi Dayan
2020-11-02 14:47 ` Roi Dayan
2020-11-01 20:15 ` [PATCH mlx5-next v1 03/11] net/mlx5_core: Clean driver version and name Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-02 5:07 ` Parav Pandit
2020-11-02 5:07 ` Parav Pandit
2020-11-02 5:56 ` Leon Romanovsky
2020-11-02 5:56 ` Leon Romanovsky
2020-11-02 5:56 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 04/11] vdpa/mlx5: Make hardware definitions visible to all mlx5 devices Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-05 20:31 ` Saeed Mahameed
2020-11-05 20:31 ` Saeed Mahameed
2020-11-05 20:36 ` Jason Gunthorpe
2020-11-05 20:36 ` Jason Gunthorpe
2020-11-06 7:05 ` Leon Romanovsky
2020-11-06 7:05 ` Leon Romanovsky
2020-11-06 7:05 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 05/11] net/mlx5: Register mlx5 devices to auxiliary virtual bus Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-05 20:59 ` Saeed Mahameed
2020-11-05 20:59 ` Saeed Mahameed
2020-11-05 21:09 ` Jason Gunthorpe
2020-11-05 21:09 ` Jason Gunthorpe
2020-11-06 6:56 ` Leon Romanovsky
2020-11-06 6:56 ` Leon Romanovsky
2020-11-06 6:56 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 06/11] vdpa/mlx5: Connect mlx5_vdpa to auxiliary bus Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-03 15:45 ` Jason Gunthorpe
2020-11-03 15:45 ` Jason Gunthorpe
2020-11-03 15:45 ` Jason Gunthorpe
2020-11-04 23:21 ` Dan Williams
2020-11-04 23:21 ` Dan Williams
2020-11-04 23:21 ` Dan Williams
2020-11-05 7:33 ` gregkh [this message]
2020-11-05 7:33 ` gregkh
2020-11-05 7:33 ` gregkh
2020-11-05 7:49 ` Dan Williams
2020-11-05 7:49 ` Dan Williams
2020-11-05 7:49 ` Dan Williams
2020-11-05 16:47 ` Jason Gunthorpe
2020-11-05 16:47 ` Jason Gunthorpe
2020-11-05 16:47 ` Jason Gunthorpe
2020-11-05 16:57 ` gregkh
2020-11-05 16:57 ` gregkh
2020-11-05 16:57 ` gregkh
2020-11-01 20:15 ` [PATCH mlx5-next v1 07/11] net/mlx5e: Connect ethernet part " Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 08/11] RDMA/mlx5: Convert mlx5_ib to use " Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 09/11] net/mlx5: Delete custom device management logic Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` [PATCH mlx5-next v1 10/11] net/mlx5: Simplify eswitch mode check Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-02 14:54 ` Roi Dayan
2020-11-02 14:54 ` Roi Dayan
2020-11-01 20:15 ` [PATCH mlx5-next v1 11/11] RDMA/mlx5: Remove IB representors dead code Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-01 20:15 ` Leon Romanovsky
2020-11-03 7:10 ` Roi Dayan
2020-11-03 7:10 ` Roi Dayan
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=20201105073302.GA3415673@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=dledford@redhat.com \
--cc=fred.oh@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kiran.patil@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shiraz.saleem@intel.com \
--cc=tiwai@suse.de \
--cc=virtualization@lists.linux-foundation.org \
/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.