All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org, kwankhede@nvidia.com,
	alex.williamson@redhat.com, tiwei.bie@intel.com,
	virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, cohuck@redhat.com,
	maxime.coquelin@redhat.com, cunming.liang@intel.com,
	zhihong.wang@intel.com, rob.miller@broadcom.com,
	xiao.w.wang@intel.com, haotian.wang@sifive.com,
	zhenyuw@linux.intel.com, zhi.a.wang@intel.com,
	jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	rodrigo.vivi@intel.com, airlied@linux.ie, daniel@ffwll.ch,
	farman@linux.ibm.com, pasic@linux.ibm.com, sebott@linux.ibm.com,
	oberpar@linux.ibm.com, heiko.carstens@de.ibm.com,
	gor@linux.ibm.com, borntraeger@de.ibm.com,
	akrowiak@linux.ibm.com, freude@linux.ibm.com,
	lingshan.zhu@intel.com, eperezma@redhat.com, lulu@redhat.com,
	parav@mellanox.com, christophe.de.dinechin@gmail.com,
	kevin.tian@intel.com, stefanha@redhat.com, rdunlap@infradead.org,
	hch@infradead.org, gregkh@linuxfoundation.org, jgg@mellanox.com
Subject: Re: [PATCH V12 5/6] virtio: introduce a mdev based transport
Date: Mon, 18 Nov 2019 18:56:52 +0800	[thread overview]
Message-ID: <a59bf414-aefb-954c-86ea-b970513171bf@redhat.com> (raw)
In-Reply-To: <20191118054339-mutt-send-email-mst@kernel.org>


On 2019/11/18 下午6:44, Michael S. Tsirkin wrote:
>> +static const struct mdev_virtio_class_id virtio_id_table[] = {
>> +	{ MDEV_VIRTIO_CLASS_ID_VIRTIO },
>> +	{ 0 },
>> +};
>> +
> Do we still need the class ID? It's a virtio mdev bus,
> do we need a virtio class as well?
>

If we want to have auto match between vhost-mdev driver and vhost-mdev 
device, we need this.

Otherwise, user need to manually probe or bind driver to the device.

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org, kwankhede@nvidia.com,
	alex.williamson@redhat.com, tiwei.bie@intel.com,
	virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, cohuck@redhat.com,
	maxime.coquelin@redhat.com, cunming.liang@intel.com,
	zhihong.wang@intel.com, rob.miller@broadcom.com,
	xiao.w.wang@intel.com, haotian.wang@sifive.com,
	zhenyuw@linux.intel.com, zhi.a.wang@intel.com,
	jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	rodrigo.vivi@intel.com, airlied@linux.ie, daniel@ffwll.ch,
	farman@linux.ibm.com, pasic@linux.ibm.com, sebott@linux.ibm.com,
	oberpar@linux.ibm.com, heiko.carstens@de.ibm.com, gor@linux.ib
Subject: Re: [PATCH V12 5/6] virtio: introduce a mdev based transport
Date: Mon, 18 Nov 2019 18:56:52 +0800	[thread overview]
Message-ID: <a59bf414-aefb-954c-86ea-b970513171bf@redhat.com> (raw)
In-Reply-To: <20191118054339-mutt-send-email-mst@kernel.org>


On 2019/11/18 下午6:44, Michael S. Tsirkin wrote:
>> +static const struct mdev_virtio_class_id virtio_id_table[] = {
>> +	{ MDEV_VIRTIO_CLASS_ID_VIRTIO },
>> +	{ 0 },
>> +};
>> +
> Do we still need the class ID? It's a virtio mdev bus,
> do we need a virtio class as well?
>

If we want to have auto match between vhost-mdev driver and vhost-mdev 
device, we need this.

Otherwise, user need to manually probe or bind driver to the device.

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: rdunlap@infradead.org, christophe.de.dinechin@gmail.com,
	kvm@vger.kernel.org, hch@infradead.org, airlied@linux.ie,
	heiko.carstens@de.ibm.com, kevin.tian@intel.com,
	dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org, kwankhede@nvidia.com,
	jgg@mellanox.com, rob.miller@broadcom.com,
	linux-s390@vger.kernel.org, sebott@linux.ibm.com,
	lulu@redhat.com, eperezma@redhat.com, pasic@linux.ibm.com,
	borntraeger@de.ibm.com, haotian.wang@sifive.com,
	cunming.liang@intel.com, zhi.a.wang@intel.com,
	farman@linux.ibm.com, parav@mellanox.com, gor@linux.ibm.com,
	intel-gfx@lists.freedesktop.org, alex.williamson@redhat.com,
	xiao.w.wang@intel.com, freude@linux.ibm.com, stefanha@redhat.com,
	zhihong.wang@intel.com, rodrigo.vivi@intel.com,
	intel-gvt-dev@lists.freedesktop.org, akrowiak@linux.ibm.com,
	oberpar@linux.ibm.com, tiwei.bie@intel.com,
	netdev@vger.kernel.org, cohuck@redhat.com,
	linux-kernel@vger.kernel.org, maxime.coquelin@redhat.com,
	gregkh@linuxfoundation.org, lingshan.zhu@intel.com
Subject: Re: [PATCH V12 5/6] virtio: introduce a mdev based transport
Date: Mon, 18 Nov 2019 18:56:52 +0800	[thread overview]
Message-ID: <a59bf414-aefb-954c-86ea-b970513171bf@redhat.com> (raw)
Message-ID: <20191118105652.e_WOUb_nyX7L08QXkOGQ_gRqQ0aawycW3_wXzlpwxho@z> (raw)
In-Reply-To: <20191118054339-mutt-send-email-mst@kernel.org>


On 2019/11/18 下午6:44, Michael S. Tsirkin wrote:
>> +static const struct mdev_virtio_class_id virtio_id_table[] = {
>> +	{ MDEV_VIRTIO_CLASS_ID_VIRTIO },
>> +	{ 0 },
>> +};
>> +
> Do we still need the class ID? It's a virtio mdev bus,
> do we need a virtio class as well?
>

If we want to have auto match between vhost-mdev driver and vhost-mdev 
device, we need this.

Otherwise, user need to manually probe or bind driver to the device.

Thanks

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: rdunlap@infradead.org, christophe.de.dinechin@gmail.com,
	kvm@vger.kernel.org, hch@infradead.org, airlied@linux.ie,
	heiko.carstens@de.ibm.com, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org, kwankhede@nvidia.com,
	jgg@mellanox.com, rob.miller@broadcom.com,
	linux-s390@vger.kernel.org, sebott@linux.ibm.com,
	lulu@redhat.com, eperezma@redhat.com, pasic@linux.ibm.com,
	borntraeger@de.ibm.com, haotian.wang@sifive.com,
	cunming.liang@intel.com, farman@linux.ibm.com,
	parav@mellanox.com, gor@linux.ibm.com,
	intel-gfx@lists.freedesktop.org, xiao.w.wang@intel.com,
	freude@linux.ibm.com, stefanha@redhat.com,
	zhihong.wang@intel.com, intel-gvt-dev@lists.freedesktop.org,
	akrowiak@linux.ibm.com, oberpar@linux.ibm.com,
	tiwei.bie@intel.com, netdev@vger.kernel.org, cohuck@redhat.com,
	linux-kernel@vger.kernel.org, maxime.coquelin@redhat.com,
	gregkh@linuxfoundation.org, lingshan.zhu@intel.com
Subject: Re: [Intel-gfx] [PATCH V12 5/6] virtio: introduce a mdev based transport
Date: Mon, 18 Nov 2019 18:56:52 +0800	[thread overview]
Message-ID: <a59bf414-aefb-954c-86ea-b970513171bf@redhat.com> (raw)
Message-ID: <20191118105652.if9OkOzFu5aXghf1-X4IgxUhsyQsUXPtNlyV8wWqXC0@z> (raw)
In-Reply-To: <20191118054339-mutt-send-email-mst@kernel.org>


On 2019/11/18 下午6:44, Michael S. Tsirkin wrote:
>> +static const struct mdev_virtio_class_id virtio_id_table[] = {
>> +	{ MDEV_VIRTIO_CLASS_ID_VIRTIO },
>> +	{ 0 },
>> +};
>> +
> Do we still need the class ID? It's a virtio mdev bus,
> do we need a virtio class as well?
>

If we want to have auto match between vhost-mdev driver and vhost-mdev 
device, we need this.

Otherwise, user need to manually probe or bind driver to the device.

Thanks

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-11-18 10:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18  6:16 [PATCH V12 0/6] mdev based hardware virtio offloading support Jason Wang
2019-11-18  6:16 ` [Intel-gfx] " Jason Wang
2019-11-18  6:16 ` Jason Wang
2019-11-18  6:16 ` Jason Wang
2019-11-18  6:16 ` [PATCH V12 1/6] mdev: make mdev bus agnostic Jason Wang
2019-11-18  6:16   ` [Intel-gfx] " Jason Wang
2019-11-18  6:16   ` Jason Wang
2019-11-18  6:16   ` Jason Wang
2019-11-18  6:16 ` [PATCH V12 2/6] mdev: split out VFIO bus specific parent ops Jason Wang
2019-11-18  6:16   ` [Intel-gfx] " Jason Wang
2019-11-18  6:16   ` Jason Wang
2019-11-18  6:16   ` Jason Wang
2019-11-18  6:17 ` [PATCH V12 3/6] mdev: move to drivers/ Jason Wang
2019-11-18  6:17   ` [Intel-gfx] " Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18  6:17 ` [PATCH V12 4/6] mdev: introduce mediated virtio bus Jason Wang
2019-11-18  6:17   ` [Intel-gfx] " Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18  6:17 ` [PATCH V12 5/6] virtio: introduce a mdev based transport Jason Wang
2019-11-18  6:17   ` [Intel-gfx] " Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18 10:44   ` Michael S. Tsirkin
2019-11-18 10:44     ` [Intel-gfx] " Michael S. Tsirkin
2019-11-18 10:44     ` Michael S. Tsirkin
2019-11-18 10:44     ` Michael S. Tsirkin
2019-11-18 10:56     ` Jason Wang [this message]
2019-11-18 10:56       ` [Intel-gfx] " Jason Wang
2019-11-18 10:56       ` Jason Wang
2019-11-18 10:56       ` Jason Wang
2019-11-18  6:17 ` [PATCH V12 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework Jason Wang
2019-11-18  6:17   ` [Intel-gfx] " Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18  6:17   ` Jason Wang
2019-11-18  6:58 ` ✗ Fi.CI.BUILD: failure for mdev based hardware virtio offloading support Patchwork
2019-11-18  6:58   ` [Intel-gfx] " Patchwork
2019-11-18 10:42 ` [PATCH V12 0/6] " Jason Wang
2019-11-18 10:42   ` [Intel-gfx] " Jason Wang
2019-11-18 10:42   ` Jason Wang

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=a59bf414-aefb-954c-86ea-b970513171bf@redhat.com \
    --to=jasowang@redhat.com \
    --cc=airlied@linux.ie \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=christophe.de.dinechin@gmail.com \
    --cc=cohuck@redhat.com \
    --cc=cunming.liang@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eperezma@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haotian.wang@sifive.com \
    --cc=hch@infradead.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jgg@mellanox.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=lingshan.zhu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lulu@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=oberpar@linux.ibm.com \
    --cc=parav@mellanox.com \
    --cc=pasic@linux.ibm.com \
    --cc=rdunlap@infradead.org \
    --cc=rob.miller@broadcom.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sebott@linux.ibm.com \
    --cc=stefanha@redhat.com \
    --cc=tiwei.bie@intel.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xiao.w.wang@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@intel.com \
    --cc=zhihong.wang@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.