From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: 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, parav@mellanox.com,
Kiran Patil <kiran.patil@intel.com>
Subject: Re: [net-next 1/1] virtual-bus: Implementation of Virtual Bus
Date: Tue, 12 Nov 2019 16:59:58 -0400 [thread overview]
Message-ID: <20191112205958.GH5584@ziepe.ca> (raw)
In-Reply-To: <20191111192219.30259-1-jeffrey.t.kirsher@intel.com>
On Mon, Nov 11, 2019 at 11:22:19AM -0800, Jeff Kirsher wrote:
> From: Dave Ertman <david.m.ertman@intel.com>
>
> This is the initial implementation of the Virtual Bus,
> virtbus_device and virtbus_driver. The virtual bus is
> a software based bus intended to support lightweight
> devices and drivers and provide matching between them
> and probing of the registered drivers.
>
> Files added:
> drivers/bus/virtual_bus.c
> include/linux/virtual_bus.h
> Documentation/driver-api/virtual_bus.rst
>
> The primary purpose of the virual bus is to provide
> matching services and to pass the data pointer
> contained in the virtbus_device to the virtbus_driver
> during its probe call. This will allow two separate
> kernel objects to match up and start communication.
I think this is the 'multi_subsystem_device' idea I threw out in this
thread. ie pass an opaque void *pointer, done here by
virtbus_get_devdata():
https://lore.kernel.org/r/20191109084659.GB1289838@kroah.com
And Greg said 'Ick, no'..
So each driver should makes its own bus, and perhaps we should provide
some helper stuff for the repeating code, like PM function reflection?
Jason
next prev parent reply other threads:[~2019-11-12 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 19:22 [net-next 1/1] virtual-bus: Implementation of Virtual Bus Jeff Kirsher
2019-11-12 20:59 ` Jason Gunthorpe [this message]
2019-11-12 21:18 ` Ertman, David M
2019-11-12 21:28 ` Greg KH
2019-11-13 0:08 ` Jason Gunthorpe
2019-11-13 1:03 ` Parav Pandit
2019-11-13 1:10 ` Jason Gunthorpe
2019-11-13 6:44 ` Parav Pandit
2019-11-13 1:09 ` Ertman, David M
2019-11-13 7:03 ` Parav Pandit
2019-11-15 21:17 ` 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=20191112205958.GH5584@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--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 \
/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).