From: Jason Wang <jasowang@redhat.com>
To: Cornelia Huck <cohuck@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, mst@redhat.com, tiwei.bie@intel.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, 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 V9 5/6] virtio: introduce a mdev based transport
Date: Wed, 6 Nov 2019 21:11:15 +0800 [thread overview]
Message-ID: <46df7afa-7543-ce19-7ede-9041907e2730@redhat.com> (raw)
In-Reply-To: <20191106120047.5bcf49c3.cohuck@redhat.com>
On 2019/11/6 下午7:00, Cornelia Huck wrote:
> On Wed, 6 Nov 2019 15:05:47 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> This patch introduces a new mdev transport for virtio. This is used to
>> use kernel virtio driver to drive the mediated device that is capable
>> of populating virtqueue directly.
>>
>> A new virtio-mdev driver will be registered to the mdev bus, when a
>> new virtio-mdev device is probed, it will register the device with
>> mdev based config ops. This means it is a software transport between
>> mdev driver and mdev device. The transport was implemented through
>> device specific ops which is a part of mdev_parent_ops now.
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/virtio/Kconfig | 13 ++
>> drivers/virtio/Makefile | 1 +
>> drivers/virtio/virtio_mdev.c | 406 +++++++++++++++++++++++++++++++++++
>> 3 files changed, 420 insertions(+)
>> create mode 100644 drivers/virtio/virtio_mdev.c
>>
>> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
>> index 078615cf2afc..558ac607d107 100644
>> --- a/drivers/virtio/Kconfig
>> +++ b/drivers/virtio/Kconfig
>> @@ -43,6 +43,19 @@ config VIRTIO_PCI_LEGACY
>>
>> If unsure, say Y.
>>
>> +config VIRTIO_MDEV
>> + tristate "MDEV driver for virtio devices"
>> + depends on VFIO_MDEV && VIRTIO
>> + default n
>> + help
>> + This driver provides support for virtio based paravirtual
>> + device driver over MDEV bus. This requires your environemnt
>> + has appropriate virtio mdev device implementation which may
>> + operate on the physical device that the datapath of virtio
>> + could be offloaded to hardware.
> That sentence is a bit confusing to me... what about
>
> "For this to be useful, you need an appropriate virtio mdev device
> implementation that operates on a physical device to allow the datapath
> of virtio to be offloaded to hardware."
>
> ?
>
>> +
>> + If unsure, say M
> Building this as a module should not hurt (but please add a trailing
> '.' here :)
>
>> +
>> config VIRTIO_PMEM
>> tristate "Support for virtio pmem driver"
>> depends on VIRTIO
> With the changes above,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
Will post V10.
Thanks
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: Cornelia Huck <cohuck@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, mst@redhat.com, tiwei.bie@intel.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, 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.c
Subject: Re: [PATCH V9 5/6] virtio: introduce a mdev based transport
Date: Wed, 6 Nov 2019 21:11:15 +0800 [thread overview]
Message-ID: <46df7afa-7543-ce19-7ede-9041907e2730@redhat.com> (raw)
In-Reply-To: <20191106120047.5bcf49c3.cohuck@redhat.com>
On 2019/11/6 下午7:00, Cornelia Huck wrote:
> On Wed, 6 Nov 2019 15:05:47 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> This patch introduces a new mdev transport for virtio. This is used to
>> use kernel virtio driver to drive the mediated device that is capable
>> of populating virtqueue directly.
>>
>> A new virtio-mdev driver will be registered to the mdev bus, when a
>> new virtio-mdev device is probed, it will register the device with
>> mdev based config ops. This means it is a software transport between
>> mdev driver and mdev device. The transport was implemented through
>> device specific ops which is a part of mdev_parent_ops now.
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/virtio/Kconfig | 13 ++
>> drivers/virtio/Makefile | 1 +
>> drivers/virtio/virtio_mdev.c | 406 +++++++++++++++++++++++++++++++++++
>> 3 files changed, 420 insertions(+)
>> create mode 100644 drivers/virtio/virtio_mdev.c
>>
>> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
>> index 078615cf2afc..558ac607d107 100644
>> --- a/drivers/virtio/Kconfig
>> +++ b/drivers/virtio/Kconfig
>> @@ -43,6 +43,19 @@ config VIRTIO_PCI_LEGACY
>>
>> If unsure, say Y.
>>
>> +config VIRTIO_MDEV
>> + tristate "MDEV driver for virtio devices"
>> + depends on VFIO_MDEV && VIRTIO
>> + default n
>> + help
>> + This driver provides support for virtio based paravirtual
>> + device driver over MDEV bus. This requires your environemnt
>> + has appropriate virtio mdev device implementation which may
>> + operate on the physical device that the datapath of virtio
>> + could be offloaded to hardware.
> That sentence is a bit confusing to me... what about
>
> "For this to be useful, you need an appropriate virtio mdev device
> implementation that operates on a physical device to allow the datapath
> of virtio to be offloaded to hardware."
>
> ?
>
>> +
>> + If unsure, say M
> Building this as a module should not hurt (but please add a trailing
> '.' here :)
>
>> +
>> config VIRTIO_PMEM
>> tristate "Support for virtio pmem driver"
>> depends on VIRTIO
> With the changes above,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
Will post V10.
Thanks
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: Cornelia Huck <cohuck@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,
alex.williamson@redhat.com, xiao.w.wang@intel.com,
freude@linux.ibm.com, parav@mellanox.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,
linux-kernel@vger.kernel.org, maxime.coquelin@redhat.com,
lingshan.zhu@intel.com
Subject: Re: [PATCH V9 5/6] virtio: introduce a mdev based transport
Date: Wed, 6 Nov 2019 21:11:15 +0800 [thread overview]
Message-ID: <46df7afa-7543-ce19-7ede-9041907e2730@redhat.com> (raw)
Message-ID: <20191106131115.oIGYxyWMUvkDbLw9QKDLlon4f8C0_O0Ny91zT8zMJBI@z> (raw)
In-Reply-To: <20191106120047.5bcf49c3.cohuck@redhat.com>
On 2019/11/6 下午7:00, Cornelia Huck wrote:
> On Wed, 6 Nov 2019 15:05:47 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> This patch introduces a new mdev transport for virtio. This is used to
>> use kernel virtio driver to drive the mediated device that is capable
>> of populating virtqueue directly.
>>
>> A new virtio-mdev driver will be registered to the mdev bus, when a
>> new virtio-mdev device is probed, it will register the device with
>> mdev based config ops. This means it is a software transport between
>> mdev driver and mdev device. The transport was implemented through
>> device specific ops which is a part of mdev_parent_ops now.
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/virtio/Kconfig | 13 ++
>> drivers/virtio/Makefile | 1 +
>> drivers/virtio/virtio_mdev.c | 406 +++++++++++++++++++++++++++++++++++
>> 3 files changed, 420 insertions(+)
>> create mode 100644 drivers/virtio/virtio_mdev.c
>>
>> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
>> index 078615cf2afc..558ac607d107 100644
>> --- a/drivers/virtio/Kconfig
>> +++ b/drivers/virtio/Kconfig
>> @@ -43,6 +43,19 @@ config VIRTIO_PCI_LEGACY
>>
>> If unsure, say Y.
>>
>> +config VIRTIO_MDEV
>> + tristate "MDEV driver for virtio devices"
>> + depends on VFIO_MDEV && VIRTIO
>> + default n
>> + help
>> + This driver provides support for virtio based paravirtual
>> + device driver over MDEV bus. This requires your environemnt
>> + has appropriate virtio mdev device implementation which may
>> + operate on the physical device that the datapath of virtio
>> + could be offloaded to hardware.
> That sentence is a bit confusing to me... what about
>
> "For this to be useful, you need an appropriate virtio mdev device
> implementation that operates on a physical device to allow the datapath
> of virtio to be offloaded to hardware."
>
> ?
>
>> +
>> + If unsure, say M
> Building this as a module should not hurt (but please add a trailing
> '.' here :)
>
>> +
>> config VIRTIO_PMEM
>> tristate "Support for virtio pmem driver"
>> depends on VIRTIO
> With the changes above,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
Will post V10.
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: Cornelia Huck <cohuck@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, linux-kernel@vger.kernel.org,
maxime.coquelin@redhat.com, lingshan.zhu@intel.com
Subject: Re: [Intel-gfx] [PATCH V9 5/6] virtio: introduce a mdev based transport
Date: Wed, 6 Nov 2019 21:11:15 +0800 [thread overview]
Message-ID: <46df7afa-7543-ce19-7ede-9041907e2730@redhat.com> (raw)
Message-ID: <20191106131115.yMSak_f_eJ076vGy928CuzgI95WFUmSVKd9o2Zu20Xo@z> (raw)
In-Reply-To: <20191106120047.5bcf49c3.cohuck@redhat.com>
On 2019/11/6 下午7:00, Cornelia Huck wrote:
> On Wed, 6 Nov 2019 15:05:47 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> This patch introduces a new mdev transport for virtio. This is used to
>> use kernel virtio driver to drive the mediated device that is capable
>> of populating virtqueue directly.
>>
>> A new virtio-mdev driver will be registered to the mdev bus, when a
>> new virtio-mdev device is probed, it will register the device with
>> mdev based config ops. This means it is a software transport between
>> mdev driver and mdev device. The transport was implemented through
>> device specific ops which is a part of mdev_parent_ops now.
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/virtio/Kconfig | 13 ++
>> drivers/virtio/Makefile | 1 +
>> drivers/virtio/virtio_mdev.c | 406 +++++++++++++++++++++++++++++++++++
>> 3 files changed, 420 insertions(+)
>> create mode 100644 drivers/virtio/virtio_mdev.c
>>
>> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
>> index 078615cf2afc..558ac607d107 100644
>> --- a/drivers/virtio/Kconfig
>> +++ b/drivers/virtio/Kconfig
>> @@ -43,6 +43,19 @@ config VIRTIO_PCI_LEGACY
>>
>> If unsure, say Y.
>>
>> +config VIRTIO_MDEV
>> + tristate "MDEV driver for virtio devices"
>> + depends on VFIO_MDEV && VIRTIO
>> + default n
>> + help
>> + This driver provides support for virtio based paravirtual
>> + device driver over MDEV bus. This requires your environemnt
>> + has appropriate virtio mdev device implementation which may
>> + operate on the physical device that the datapath of virtio
>> + could be offloaded to hardware.
> That sentence is a bit confusing to me... what about
>
> "For this to be useful, you need an appropriate virtio mdev device
> implementation that operates on a physical device to allow the datapath
> of virtio to be offloaded to hardware."
>
> ?
>
>> +
>> + If unsure, say M
> Building this as a module should not hurt (but please add a trailing
> '.' here :)
>
>> +
>> config VIRTIO_PMEM
>> tristate "Support for virtio pmem driver"
>> depends on VIRTIO
> With the changes above,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
Will post V10.
Thanks
_______________________________________________
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-06 13:12 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 7:05 [PATCH V9 0/6] mdev based hardware virtio offloading support Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [PATCH V9 1/6] mdev: class id support Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [PATCH V9 2/6] modpost: add support for mdev class id Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [PATCH V9 3/6] mdev: introduce device specific ops Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 10:52 ` Cornelia Huck
2019-11-06 10:52 ` [Intel-gfx] " Cornelia Huck
2019-11-06 10:52 ` Cornelia Huck
2019-11-06 10:52 ` Cornelia Huck
2019-11-06 10:52 ` Cornelia Huck
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [PATCH V9 4/6] mdev: introduce virtio device and its device ops Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 10:53 ` Cornelia Huck
2019-11-06 10:53 ` Cornelia Huck
2019-11-06 10:53 ` [Intel-gfx] " Cornelia Huck
2019-11-06 10:53 ` Cornelia Huck
2019-11-06 10:53 ` Cornelia Huck
2019-11-06 7:05 ` [PATCH V9 5/6] virtio: introduce a mdev based transport Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 11:00 ` Cornelia Huck
2019-11-06 11:00 ` [Intel-gfx] " Cornelia Huck
2019-11-06 11:00 ` Cornelia Huck
2019-11-06 11:00 ` Cornelia Huck
2019-11-06 13:11 ` Jason Wang [this message]
2019-11-06 13:11 ` [Intel-gfx] " Jason Wang
2019-11-06 13:11 ` Jason Wang
2019-11-06 13:11 ` Jason Wang
2019-11-06 13:11 ` Jason Wang
2019-11-06 11:00 ` Cornelia Huck
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` [PATCH V9 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework Jason Wang
2019-11-06 7:05 ` [Intel-gfx] " Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 7:05 ` Jason Wang
2019-11-06 22:50 ` Randy Dunlap
2019-11-06 22:50 ` [Intel-gfx] " Randy Dunlap
2019-11-06 22:50 ` Randy Dunlap
2019-11-06 22:58 ` Alex Williamson
2019-11-06 22:58 ` [Intel-gfx] " Alex Williamson
2019-11-06 22:58 ` Alex Williamson
2019-11-06 22:58 ` Alex Williamson
2019-11-07 14:30 ` Jason Wang
2019-11-07 14:30 ` Jason Wang
2019-11-07 14:30 ` [Intel-gfx] " Jason Wang
2019-11-07 14:30 ` Jason Wang
2019-11-07 14:30 ` Jason Wang
2019-11-06 22:58 ` Alex Williamson
2019-11-06 22:50 ` Randy Dunlap
2019-11-06 7:35 ` ✗ Fi.CI.CHECKPATCH: warning for mdev based hardware virtio offloading support Patchwork
2019-11-06 7:35 ` [Intel-gfx] " Patchwork
2019-11-06 7:56 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-06 7:56 ` [Intel-gfx] " Patchwork
2019-11-07 1:13 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-07 1:13 ` [Intel-gfx] " Patchwork
2019-11-07 1:37 ` ✗ Fi.CI.BUILD: failure for mdev based hardware virtio offloading support (rev2) Patchwork
2019-11-07 1:37 ` [Intel-gfx] " Patchwork
2019-11-07 9:01 ` [PATCH V9 0/6] mdev based hardware virtio offloading support Michael S. Tsirkin
2019-11-07 9:01 ` Michael S. Tsirkin
2019-11-07 9:01 ` [Intel-gfx] " Michael S. Tsirkin
2019-11-07 9:01 ` Michael S. Tsirkin
2019-11-07 9:01 ` Michael S. Tsirkin
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=46df7afa-7543-ce19-7ede-9041907e2730@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=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=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.