From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Wang <jasowang@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,
mst@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, idos@mellanox.com, eperezma@redhat.com,
lulu@redhat.com, parav@mellanox.com,
christophe.de.dinechin@gmail.com, kevin.tian@intel.com,
stefanha@redhat.com
Subject: Re: [PATCH V8 0/6] mdev based hardware virtio offloading support
Date: Tue, 5 Nov 2019 10:58:34 -0700 [thread overview]
Message-ID: <20191105105834.469675f0@x1.home> (raw)
In-Reply-To: <20191105093240.5135-1-jasowang@redhat.com>
On Tue, 5 Nov 2019 17:32:34 +0800
Jason Wang <jasowang@redhat.com> wrote:
> Hi all:
>
> There are hardwares that can do virtio datapath offloading while
> having its own control path. This path tries to implement a mdev based
> unified API to support using kernel virtio driver to drive those
> devices. This is done by introducing a new mdev transport for virtio
> (virtio_mdev) and register itself as a new kind of mdev driver. Then
> it provides a unified way for kernel virtio driver to talk with mdev
> device implementation.
>
> Though the series only contains kernel driver support, the goal is to
> make the transport generic enough to support userspace drivers. This
> means vhost-mdev[1] could be built on top as well by resuing the
> transport.
>
> A sample driver is also implemented which simulate a virito-net
> loopback ethernet device on top of vringh + workqueue. This could be
> used as a reference implementation for real hardware driver.
>
> Also a real ICF VF driver was also posted here[2] which is a good
> reference for vendors who is interested in their own virtio datapath
> offloading product.
>
> Consider mdev framework only support VFIO device and driver right now,
> this series also extend it to support other types. This is done
> through introducing class id to the device and pairing it with
> id_talbe claimed by the driver. On top, this seris also decouple
> device specific parents ops out of the common ones.
>
> Pktgen test was done with virito-net + mvnet loop back device.
>
> Please review.
>
> [1] https://lkml.org/lkml/2019/10/31/440
> [2] https://lkml.org/lkml/2019/10/15/1226
>
> Changes from V7:
> - drop {set|get}_mdev_features for virtio
> - typo and comment style fixes
Seems we're nearly there, all the remaining comments are relatively
superficial, though I would appreciate a v9 addressing them as well as
the checkpatch warnings:
https://patchwork.freedesktop.org/series/68977/
Consider this a last call for reviews or acks (or naks) from affected
mdev vendor drivers, mdev-core sub-maintainers (Hi Kirti), virtio
stakeholders, etc. Thanks,
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: stefanha@redhat.com, christophe.de.dinechin@gmail.com,
kvm@vger.kernel.org, mst@redhat.com, airlied@linux.ie,
heiko.carstens@de.ibm.com, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org, kwankhede@nvidia.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, idos@mellanox.com, gor@linux.ibm.com,
intel-gfx@lists.freedesktop.org, xiao.w.wang@intel.com,
freude@linux.ibm.com, parav@mellanox.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,
lingshan.zhu@intel.com
Subject: Re: [PATCH V8 0/6] mdev based hardware virtio offloading support
Date: Tue, 5 Nov 2019 10:58:34 -0700 [thread overview]
Message-ID: <20191105105834.469675f0@x1.home> (raw)
In-Reply-To: <20191105093240.5135-1-jasowang@redhat.com>
On Tue, 5 Nov 2019 17:32:34 +0800
Jason Wang <jasowang@redhat.com> wrote:
> Hi all:
>
> There are hardwares that can do virtio datapath offloading while
> having its own control path. This path tries to implement a mdev based
> unified API to support using kernel virtio driver to drive those
> devices. This is done by introducing a new mdev transport for virtio
> (virtio_mdev) and register itself as a new kind of mdev driver. Then
> it provides a unified way for kernel virtio driver to talk with mdev
> device implementation.
>
> Though the series only contains kernel driver support, the goal is to
> make the transport generic enough to support userspace drivers. This
> means vhost-mdev[1] could be built on top as well by resuing the
> transport.
>
> A sample driver is also implemented which simulate a virito-net
> loopback ethernet device on top of vringh + workqueue. This could be
> used as a reference implementation for real hardware driver.
>
> Also a real ICF VF driver was also posted here[2] which is a good
> reference for vendors who is interested in their own virtio datapath
> offloading product.
>
> Consider mdev framework only support VFIO device and driver right now,
> this series also extend it to support other types. This is done
> through introducing class id to the device and pairing it with
> id_talbe claimed by the driver. On top, this seris also decouple
> device specific parents ops out of the common ones.
>
> Pktgen test was done with virito-net + mvnet loop back device.
>
> Please review.
>
> [1] https://lkml.org/lkml/2019/10/31/440
> [2] https://lkml.org/lkml/2019/10/15/1226
>
> Changes from V7:
> - drop {set|get}_mdev_features for virtio
> - typo and comment style fixes
Seems we're nearly there, all the remaining comments are relatively
superficial, though I would appreciate a v9 addressing them as well as
the checkpatch warnings:
https://patchwork.freedesktop.org/series/68977/
Consider this a last call for reviews or acks (or naks) from affected
mdev vendor drivers, mdev-core sub-maintainers (Hi Kirti), virtio
stakeholders, etc. Thanks,
Alex
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: stefanha@redhat.com, christophe.de.dinechin@gmail.com,
kvm@vger.kernel.org, mst@redhat.com, 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,
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, idos@mellanox.com,
gor@linux.ibm.com, intel-gfx@lists.freedesktop.org,
rodrigo.vivi@intel.com, xiao.w.wang@intel.com,
freude@linux.ibm.com, parav@mellanox.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,
lingshan.zhu@intel.com
Subject: Re: [PATCH V8 0/6] mdev based hardware virtio offloading support
Date: Tue, 5 Nov 2019 10:58:34 -0700 [thread overview]
Message-ID: <20191105105834.469675f0@x1.home> (raw)
Message-ID: <20191105175834.7VqDHFwT-Mdt-2ZCIPhv36gA0ul4jGdZwmPeWuGxYiM@z> (raw)
In-Reply-To: <20191105093240.5135-1-jasowang@redhat.com>
On Tue, 5 Nov 2019 17:32:34 +0800
Jason Wang <jasowang@redhat.com> wrote:
> Hi all:
>
> There are hardwares that can do virtio datapath offloading while
> having its own control path. This path tries to implement a mdev based
> unified API to support using kernel virtio driver to drive those
> devices. This is done by introducing a new mdev transport for virtio
> (virtio_mdev) and register itself as a new kind of mdev driver. Then
> it provides a unified way for kernel virtio driver to talk with mdev
> device implementation.
>
> Though the series only contains kernel driver support, the goal is to
> make the transport generic enough to support userspace drivers. This
> means vhost-mdev[1] could be built on top as well by resuing the
> transport.
>
> A sample driver is also implemented which simulate a virito-net
> loopback ethernet device on top of vringh + workqueue. This could be
> used as a reference implementation for real hardware driver.
>
> Also a real ICF VF driver was also posted here[2] which is a good
> reference for vendors who is interested in their own virtio datapath
> offloading product.
>
> Consider mdev framework only support VFIO device and driver right now,
> this series also extend it to support other types. This is done
> through introducing class id to the device and pairing it with
> id_talbe claimed by the driver. On top, this seris also decouple
> device specific parents ops out of the common ones.
>
> Pktgen test was done with virito-net + mvnet loop back device.
>
> Please review.
>
> [1] https://lkml.org/lkml/2019/10/31/440
> [2] https://lkml.org/lkml/2019/10/15/1226
>
> Changes from V7:
> - drop {set|get}_mdev_features for virtio
> - typo and comment style fixes
Seems we're nearly there, all the remaining comments are relatively
superficial, though I would appreciate a v9 addressing them as well as
the checkpatch warnings:
https://patchwork.freedesktop.org/series/68977/
Consider this a last call for reviews or acks (or naks) from affected
mdev vendor drivers, mdev-core sub-maintainers (Hi Kirti), virtio
stakeholders, etc. Thanks,
Alex
_______________________________________________
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: Alex Williamson <alex.williamson@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: stefanha@redhat.com, christophe.de.dinechin@gmail.com,
kvm@vger.kernel.org, mst@redhat.com, airlied@linux.ie,
heiko.carstens@de.ibm.com, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org, kwankhede@nvidia.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, idos@mellanox.com, gor@linux.ibm.com,
intel-gfx@lists.freedesktop.org, xiao.w.wang@intel.com,
freude@linux.ibm.com, parav@mellanox.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,
lingshan.zhu@intel.com
Subject: Re: [Intel-gfx] [PATCH V8 0/6] mdev based hardware virtio offloading support
Date: Tue, 5 Nov 2019 10:58:34 -0700 [thread overview]
Message-ID: <20191105105834.469675f0@x1.home> (raw)
Message-ID: <20191105175834.rMLi7PlQAA1GQjumOAIufyfVzcc90_--srfodnLR-G0@z> (raw)
In-Reply-To: <20191105093240.5135-1-jasowang@redhat.com>
On Tue, 5 Nov 2019 17:32:34 +0800
Jason Wang <jasowang@redhat.com> wrote:
> Hi all:
>
> There are hardwares that can do virtio datapath offloading while
> having its own control path. This path tries to implement a mdev based
> unified API to support using kernel virtio driver to drive those
> devices. This is done by introducing a new mdev transport for virtio
> (virtio_mdev) and register itself as a new kind of mdev driver. Then
> it provides a unified way for kernel virtio driver to talk with mdev
> device implementation.
>
> Though the series only contains kernel driver support, the goal is to
> make the transport generic enough to support userspace drivers. This
> means vhost-mdev[1] could be built on top as well by resuing the
> transport.
>
> A sample driver is also implemented which simulate a virito-net
> loopback ethernet device on top of vringh + workqueue. This could be
> used as a reference implementation for real hardware driver.
>
> Also a real ICF VF driver was also posted here[2] which is a good
> reference for vendors who is interested in their own virtio datapath
> offloading product.
>
> Consider mdev framework only support VFIO device and driver right now,
> this series also extend it to support other types. This is done
> through introducing class id to the device and pairing it with
> id_talbe claimed by the driver. On top, this seris also decouple
> device specific parents ops out of the common ones.
>
> Pktgen test was done with virito-net + mvnet loop back device.
>
> Please review.
>
> [1] https://lkml.org/lkml/2019/10/31/440
> [2] https://lkml.org/lkml/2019/10/15/1226
>
> Changes from V7:
> - drop {set|get}_mdev_features for virtio
> - typo and comment style fixes
Seems we're nearly there, all the remaining comments are relatively
superficial, though I would appreciate a v9 addressing them as well as
the checkpatch warnings:
https://patchwork.freedesktop.org/series/68977/
Consider this a last call for reviews or acks (or naks) from affected
mdev vendor drivers, mdev-core sub-maintainers (Hi Kirti), virtio
stakeholders, etc. Thanks,
Alex
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-05 17:58 UTC|newest]
Thread overview: 125+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:32 [PATCH V8 0/6] mdev based hardware virtio offloading support Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` [PATCH V8 1/6] mdev: class id support Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 16:03 ` Cornelia Huck
2019-11-05 16:03 ` Cornelia Huck
2019-11-05 16:03 ` [Intel-gfx] " Cornelia Huck
2019-11-05 16:03 ` Cornelia Huck
2019-11-05 16:03 ` Cornelia Huck
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` [PATCH V8 2/6] modpost: add support for mdev class id Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 16:06 ` Cornelia Huck
2019-11-05 16:06 ` Cornelia Huck
2019-11-05 16:06 ` [Intel-gfx] " Cornelia Huck
2019-11-05 16:06 ` Cornelia Huck
2019-11-05 16:06 ` Cornelia Huck
2019-11-05 9:32 ` [PATCH V8 3/6] mdev: introduce device specific ops Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 16:50 ` Cornelia Huck
2019-11-05 16:50 ` Cornelia Huck
2019-11-05 16:50 ` [Intel-gfx] " Cornelia Huck
2019-11-05 16:50 ` Cornelia Huck
2019-11-05 16:50 ` Cornelia Huck
2019-11-05 17:44 ` Alex Williamson
2019-11-05 17:44 ` [Intel-gfx] " Alex Williamson
2019-11-05 17:44 ` Alex Williamson
2019-11-05 17:44 ` Alex Williamson
2019-11-05 18:28 ` Cornelia Huck
2019-11-05 18:28 ` Cornelia Huck
2019-11-05 18:28 ` [Intel-gfx] " Cornelia Huck
2019-11-05 18:28 ` Cornelia Huck
2019-11-05 18:28 ` Cornelia Huck
2019-11-06 3:48 ` Jason Wang
2019-11-06 3:48 ` Jason Wang
2019-11-06 3:48 ` [Intel-gfx] " Jason Wang
2019-11-06 3:48 ` Jason Wang
2019-11-06 3:48 ` Jason Wang
2019-11-05 17:44 ` Alex Williamson
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` [PATCH V8 4/6] mdev: introduce virtio device and its device ops Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 16:57 ` Cornelia Huck
2019-11-05 16:57 ` [Intel-gfx] " Cornelia Huck
2019-11-05 16:57 ` Cornelia Huck
2019-11-05 16:57 ` Cornelia Huck
2019-11-05 16:57 ` Cornelia Huck
2019-11-05 17:47 ` Alex Williamson
2019-11-05 17:47 ` Alex Williamson
2019-11-05 17:47 ` [Intel-gfx] " Alex Williamson
2019-11-05 17:47 ` Alex Williamson
2019-11-05 17:47 ` Alex Williamson
2019-11-06 3:51 ` Jason Wang
2019-11-06 3:51 ` [Intel-gfx] " Jason Wang
2019-11-06 3:51 ` Jason Wang
2019-11-06 3:51 ` Jason Wang
2019-11-06 3:51 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` [PATCH V8 5/6] virtio: introduce a mdev based transport Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 18:33 ` Cornelia Huck
2019-11-05 18:33 ` [Intel-gfx] " Cornelia Huck
2019-11-05 18:33 ` Cornelia Huck
2019-11-05 18:33 ` Cornelia Huck
2019-11-05 18:33 ` Cornelia Huck
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` [PATCH V8 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework Jason Wang
2019-11-05 9:32 ` [Intel-gfx] " Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 9:32 ` Jason Wang
2019-11-05 18:35 ` Cornelia Huck
2019-11-05 18:35 ` Cornelia Huck
2019-11-05 18:35 ` [Intel-gfx] " Cornelia Huck
2019-11-05 18:35 ` Cornelia Huck
2019-11-05 18:35 ` Cornelia Huck
2019-11-05 10:26 ` ✗ Fi.CI.CHECKPATCH: warning for mdev based hardware virtio offloading support Patchwork
2019-11-05 10:26 ` [Intel-gfx] " Patchwork
2019-11-05 11:09 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-05 11:09 ` [Intel-gfx] " Patchwork
2019-11-05 17:58 ` Alex Williamson [this message]
2019-11-05 17:58 ` [Intel-gfx] [PATCH V8 0/6] " Alex Williamson
2019-11-05 17:58 ` Alex Williamson
2019-11-05 17:58 ` Alex Williamson
2019-11-06 3:56 ` Jason Wang
2019-11-06 3:56 ` [Intel-gfx] " Jason Wang
2019-11-06 3:56 ` Jason Wang
2019-11-06 3:56 ` Jason Wang
2019-11-06 19:03 ` Alex Williamson
2019-11-06 19:03 ` Alex Williamson
2019-11-06 19:03 ` [Intel-gfx] " Alex Williamson
2019-11-06 19:03 ` Alex Williamson
2019-11-06 19:03 ` Alex Williamson
2019-11-06 19:25 ` Michael S. Tsirkin
2019-11-06 19:25 ` Michael S. Tsirkin
2019-11-06 19:25 ` [Intel-gfx] " Michael S. Tsirkin
2019-11-06 19:25 ` Michael S. Tsirkin
2019-11-06 19:25 ` Michael S. Tsirkin
2019-11-06 21:13 ` Alex Williamson
2019-11-06 21:13 ` [Intel-gfx] " Alex Williamson
2019-11-06 21:13 ` Alex Williamson
2019-11-06 21:13 ` Alex Williamson
2019-11-07 4:11 ` Jason Wang
2019-11-07 4:11 ` Jason Wang
2019-11-07 4:11 ` [Intel-gfx] " Jason Wang
2019-11-07 4:11 ` Jason Wang
2019-11-07 4:11 ` Jason Wang
2019-11-06 21:13 ` Alex Williamson
2019-11-06 3:56 ` Jason Wang
2019-11-05 17:58 ` Alex Williamson
2019-11-05 20:00 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-11-05 20:00 ` [Intel-gfx] " Patchwork
2019-11-05 9:32 [PATCH V8 0/6] " 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=20191105105834.469675f0@x1.home \
--to=alex.williamson@redhat.com \
--cc=airlied@linux.ie \
--cc=akrowiak@linux.ibm.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=haotian.wang@sifive.com \
--cc=heiko.carstens@de.ibm.com \
--cc=idos@mellanox.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jasowang@redhat.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=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.