From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Amit Shah <amit@kernel.org>
Subject: Re: [RFC 0/2] virtio-rng: add a control queue
Date: Wed, 29 Jul 2020 10:15:48 -0400 [thread overview]
Message-ID: <20200729101522-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <eeb362c9-24e8-49ef-4194-617e8a2881a9@redhat.com>
On Tue, Jul 28, 2020 at 03:45:26PM +0200, Laurent Vivier wrote:
> On 29/01/2020 16:43, Stefan Hajnoczi wrote:
> > On Fri, Jan 24, 2020 at 03:05:18PM +0100, Laurent Vivier wrote:
> >> On 24/01/2020 12:02, Stefan Hajnoczi wrote:
> >>> On Thu, Jan 23, 2020 at 04:16:58PM +0100, Laurent Vivier wrote:
> >>>> The kernel needs sometime to be able to cancel an ongoing command.
> >>>>
> >>>> For instance, if the virtio-rng device uses the egd backend
> >>>> and this backend doesn't provide data, the buffer provided by the
> >>>> kernel is kept as long as it is needed.
> >>>>
> >>>> On the kernel side, a read blocks until the buffer returns from QEMU.
> >>>>
> >>>> As the read is done with a mutex held, all the hw_random interface
> >>>> hangs and we cannot switch to another hw_random backend.
> >>>>
> >>>> So this series adds a control queue to the virtio-rng device to allow
> >>>> to flush the virtio-rng input queue to release the kernel mutex and
> >>>> to allow to switch to another device.
> >>>>
> >>>> The kernel side series can be found at:
> >>>>
> >>>> https://github.com/vivier/linux/commits/virtio-rng-ctrl
> >>>>
> >>>> Laurent Vivier (2):
> >>>> virtio-rng: prepare the introduction of a control queue
> >>>> virtio-rng: add a control queue
> >>>>
> >>>> hw/core/machine.c | 1 +
> >>>> hw/virtio/trace-events | 6 ++
> >>>> hw/virtio/virtio-rng.c | 99 ++++++++++++++++++---
> >>>> include/hw/virtio/virtio-rng.h | 5 +-
> >>>> include/standard-headers/linux/virtio_rng.h | 14 +++
> >>>> 5 files changed, 111 insertions(+), 14 deletions(-)
> >>>
> >>> Where can I find the VIRTIO specification for this new virtqueue?
> >>
> >> I didn't update the specs.
> >>
> >> Is https://github.com/oasis-tcs/virtio-spec.git the document to update?
> >
> > Yes, please.
>
> I've updated the specs,
>
> Following
> https://github.com/oasis-tcs/virtio-spec/blob/master/CONTRIBUTING.md,
> I've opened an issue:
>
> https://github.com/oasis-tcs/virtio-spec/issues/83
>
> Is this the good process?
>
> Thanks,
> Laurent
It's ok but you also need to send spec patches by mail so
people can review.
next prev parent reply other threads:[~2020-07-29 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 15:16 [RFC 0/2] virtio-rng: add a control queue Laurent Vivier
2020-01-23 15:16 ` [RFC 1/2] virtio-rng: prepare the introduction of " Laurent Vivier
2020-01-23 15:17 ` [RFC 2/2] virtio-rng: add " Laurent Vivier
2020-01-24 11:02 ` [RFC 0/2] " Stefan Hajnoczi
2020-01-24 14:05 ` Laurent Vivier
2020-01-29 15:43 ` Stefan Hajnoczi
2020-07-28 13:45 ` Laurent Vivier
2020-07-29 9:42 ` Stefan Hajnoczi
2020-07-29 14:15 ` Michael S. Tsirkin [this message]
2020-01-24 12:43 ` Amit Shah
2020-01-24 13:50 ` Laurent Vivier
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=20200729101522-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=amit@kernel.org \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.