From: Stefan Hajnoczi <stefanha@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: mst@redhat.com, bhelgaas@google.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, virtio-dev@lists.oasis-open.org,
linux-pci@vger.kernel.org, dan.daly@intel.com,
mark.d.rustad@intel.com, alexander.h.duyck@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com
Subject: Re: [virtio-dev] [PATCH] virtio_pci: support enabling VFs
Date: Wed, 30 May 2018 13:29:40 +0100 [thread overview]
Message-ID: <20180530122940.GI14623@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180530085521.26583-1-tiwei.bie@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Wed, May 30, 2018 at 04:55:21PM +0800, Tiwei Bie wrote:
> There is a new feature bit allocated in virtio spec to
> support SR-IOV (Single Root I/O Virtualization):
>
> https://github.com/oasis-tcs/virtio-spec/issues/11
>
> This patch enables the support for this feature bit in
> virtio driver.
>
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> ---
> This patch depends on below proposal:
> https://lists.oasis-open.org/archives/virtio-dev/201805/msg00154.html
>
> This patch depends on below patch:
> https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/virtualization&id=8effc395c2097e258fcedfc02ed4a66d45fb4238
>
> drivers/virtio/virtio_pci_common.c | 20 ++++++++++++++++++++
> drivers/virtio/virtio_pci_modern.c | 14 ++++++++++++++
> include/uapi/linux/virtio_config.h | 7 ++++++-
> 3 files changed, 40 insertions(+), 1 deletion(-)
Looks good and matches the virtio spec change, but I'm not familiar with
PCI SR-IOV details, so not a full Reviewed-by.
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-05-30 12:29 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 8:55 [PATCH] virtio_pci: support enabling VFs Tiwei Bie
2018-05-30 8:55 ` [virtio-dev] " Tiwei Bie
2018-05-30 12:29 ` Stefan Hajnoczi [this message]
2018-05-30 12:29 ` Stefan Hajnoczi
2018-05-30 12:41 ` Michael S. Tsirkin
2018-05-30 12:41 ` [virtio-dev] " Michael S. Tsirkin
2018-05-30 12:41 ` Michael S. Tsirkin
2018-05-30 16:03 ` [virtio-dev] " Rustad, Mark D
2018-05-30 16:09 ` Michael S. Tsirkin
2018-05-30 16:09 ` Michael S. Tsirkin
2018-05-31 2:55 ` Tiwei Bie
2018-05-31 2:55 ` Tiwei Bie
2018-06-01 1:21 ` Michael S. Tsirkin
2018-06-01 1:21 ` Michael S. Tsirkin
2018-06-01 1:21 ` Michael S. Tsirkin
2018-06-01 1:36 ` Tiwei Bie
2018-06-01 1:36 ` Tiwei Bie
2018-06-01 1:36 ` Tiwei Bie
2018-05-31 2:55 ` Tiwei Bie
2018-05-30 16:09 ` Michael S. Tsirkin
2018-05-30 16:03 ` Rustad, Mark D
2018-05-30 16:10 ` Alexander Duyck
2018-05-30 16:10 ` Alexander Duyck
2018-05-30 16:22 ` Michael S. Tsirkin
2018-05-30 16:22 ` Michael S. Tsirkin
2018-05-30 16:22 ` Michael S. Tsirkin
2018-05-30 16:26 ` Duyck, Alexander H
2018-05-30 16:26 ` Duyck, Alexander H
2018-05-30 16:26 ` Duyck, Alexander H
2018-05-30 17:15 ` Michael S. Tsirkin
2018-05-30 17:15 ` Michael S. Tsirkin
2018-05-30 17:15 ` Michael S. Tsirkin
2018-05-30 16:10 ` Alexander Duyck
2018-05-30 16:22 ` Michael S. Tsirkin
2018-05-30 16:22 ` [virtio-dev] " Michael S. Tsirkin
2018-05-30 16:44 ` Rustad, Mark D
2018-05-30 16:44 ` [virtio-dev] " Rustad, Mark D
2018-05-30 16:44 ` Rustad, Mark D
2018-05-30 16:54 ` Duyck, Alexander H
2018-05-30 16:54 ` Duyck, Alexander H
2018-05-30 17:11 ` Rustad, Mark D
2018-05-30 17:11 ` [virtio-dev] " Rustad, Mark D
2018-05-30 17:11 ` Rustad, Mark D
2018-05-31 3:20 ` Tiwei Bie
2018-05-31 3:20 ` [virtio-dev] " Tiwei Bie
2018-05-31 14:27 ` Alexander Duyck
2018-05-31 14:27 ` Alexander Duyck
2018-05-31 14:27 ` [virtio-dev] " Alexander Duyck
2018-06-01 2:30 ` Tiwei Bie
2018-06-01 2:30 ` Tiwei Bie
2018-06-01 2:30 ` [virtio-dev] " Tiwei Bie
2018-05-31 3:20 ` Tiwei Bie
2018-05-30 16:54 ` Duyck, Alexander H
2018-05-30 16:22 ` 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=20180530122940.GI14623@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mst@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--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.