On Thu, May 24, 2018 at 07:21:01AM +0800, Tiwei Bie wrote:
> On Wed, May 23, 2018 at 06:43:29PM +0300, Michael S. Tsirkin wrote:
> > On Wed, May 23, 2018 at 06:36:05PM +0300, Michael S. Tsirkin wrote:
> > > On Wed, May 23, 2018 at 04:44:51PM +0300, Michael S. Tsirkin wrote:
> > > > On Thu, Apr 12,
On Wed, May 23, 2018 at 10:34:29PM +0300, Michael S. Tsirkin wrote:
> On Wed, May 23, 2018 at 08:54:47PM +0300, Michael S. Tsirkin wrote:
> > On Tue, May 22, 2018 at 06:26:15PM +0800, Tiwei Bie wrote:
> > > Allocate a feature bit for virtio devices which support SR-IOV.
> > >
> > > Suggested-by:
On Wed, May 23, 2018 at 06:43:29PM +0300, Michael S. Tsirkin wrote:
> On Wed, May 23, 2018 at 06:36:05PM +0300, Michael S. Tsirkin wrote:
> > On Wed, May 23, 2018 at 04:44:51PM +0300, Michael S. Tsirkin wrote:
> > > On Thu, Apr 12, 2018 at 11:12:28PM +0800, Tiwei Bie wrote:
> > > > When multi
On Thu, Apr 12, 2018 at 11:12:29PM +0800, Tiwei Bie wrote:
> Signed-off-by: Tiwei Bie
Thinking about it, I think we should add a protocol
feature for this. This way remote can find out whether
it's safe to send this data to us.
> ---
> hw/virtio/vhost-user.c | 41
On Wed, May 23, 2018 at 08:54:47PM +0300, Michael S. Tsirkin wrote:
> On Tue, May 22, 2018 at 06:26:15PM +0800, Tiwei Bie wrote:
> > Allocate a feature bit for virtio devices which support SR-IOV.
> >
> > Suggested-by: Michael S. Tsirkin
> > Signed-off-by: Tiwei Bie
On Wed, May 23, 2018 at 06:36:05PM +0300, Michael S. Tsirkin wrote:
> On Wed, May 23, 2018 at 04:44:51PM +0300, Michael S. Tsirkin wrote:
> > On Thu, Apr 12, 2018 at 11:12:28PM +0800, Tiwei Bie wrote:
> > > When multi queue is enabled e.g. for a virtio-net device,
> > > each queue pair will have a
On Wed, May 23, 2018 at 04:44:51PM +0300, Michael S. Tsirkin wrote:
> On Thu, Apr 12, 2018 at 11:12:28PM +0800, Tiwei Bie wrote:
> > When multi queue is enabled e.g. for a virtio-net device,
> > each queue pair will have a vhost_dev, and the only thing
> > shared between vhost devs currently is
Add VIRTIO_PCI_CAP_GROUP_ID_CFG (Group Identifier) capability to the
virtio PCI capabilities to allow for the grouping of devices.
Signed-off-by: Venu Busireddy
---
content.tex | 43 +++
1 file changed, 43 insertions(+)
diff
On Thu, Apr 12, 2018 at 11:12:28PM +0800, Tiwei Bie wrote:
> When multi queue is enabled e.g. for a virtio-net device,
> each queue pair will have a vhost_dev, and the only thing
> shared between vhost devs currently is the chardev. This
> patch introduces a vhost-user state structure which will
>
On Tue, May 22, 2018 at 08:48:58AM -0500, Venu Busireddy wrote:
> On 2018-05-22 11:03:37 +0100, Stefan Hajnoczi wrote:
> > On Fri, May 18, 2018 at 04:43:36PM -0500, Venu Busireddy wrote:
> > > On 2018-05-18 17:06:23 +0100, Stefan Hajnoczi wrote:
> > > > On Thu, May 17, 2018 at 09:06:04AM -0400,
On Wed, May 23, 2018 at 01:01:20AM -0400, Pankaj Gupta wrote:
>
> Hi Stefan,
>
> > >> We need a device ID for virtio-pmem devices. As 24 is already
> > >> requested by virtio-mem, so requesting next available(25)
> > >>
> > >> Signed-off-by: Pankaj Gupta
> > >> ---
> > >>
On Tue, May 22, 2018 at 09:11:05PM +0200, Christoffer Dall wrote:
> Only the device updates the used ring.
>
> This looks like a typo as a result of copy-paste from the description of
> the Available Ring.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/12
> Signed-off-by: Christoffer
Hello,
What is the status of vhost-pci device?
Is it already integrated into an official release ? patches ?
Best Regards
Avi
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail:
13 matches
Mail list logo