From: Cornelia Huck <cohuck@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: mst@redhat.com, stefanha@redhat.com, pbonzini@redhat.com,
virtio-dev@lists.oasis-open.org, dan.daly@intel.com,
alexander.h.duyck@intel.com, mark.d.rustad@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com
Subject: [virtio-dev] Re: [PATCH v4] content: support SR-IOV
Date: Tue, 29 May 2018 15:44:15 +0200 [thread overview]
Message-ID: <20180529154415.4b0648c4.cohuck@redhat.com> (raw)
In-Reply-To: <20180524164951.3102-1-tiwei.bie@intel.com>
On Fri, 25 May 2018 00:49:51 +0800
Tiwei Bie <tiwei.bie@intel.com> wrote:
> Allocate a feature bit for virtio devices which support SR-IOV.
>
> Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/11
> ---
> More details can be found from this thread:
> https://patchwork.kernel.org/patch/10285541/
>
> v3 -> v4:
> - Limit the feature to PCI devices with SR-IOV cap (MST);
>
> v2 -> v3:
> - Improve the wording (Cornelia);
>
> v1 -> v2:
> - s/Reserve/Allocate/ (MST);
> - Add a Fixes tag (MST);
> - Be more explicit in driver requirement (MST);
> - Remove the "device MAY fail" description (MST);
> - Rebase on IO_BARRIER patch;
>
> RFC -> v1:
> - Mention PCI in the description (Cornelia);
>
> content.tex | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
Acked-by: Cornelia Huck <cohuck@redhat.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2018-05-29 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 16:49 [virtio-dev] [PATCH v4] content: support SR-IOV Tiwei Bie
2018-05-29 13:28 ` Michael S. Tsirkin
2018-05-29 13:41 ` Tiwei Bie
2018-05-29 13:44 ` Cornelia Huck [this message]
2018-06-04 13:01 ` [virtio-dev] " Michael S. Tsirkin
2018-06-05 1:30 ` Tiwei Bie
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=20180529154415.4b0648c4.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=mark.d.rustad@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=virtio-dev@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox