All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pankaj Gupta <pagupta@redhat.com>
Cc: mst@redhat.com, amit@kernel.org, qemu-devel@nongnu.org,
	slopezpa@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] virtio-rng: process pending requests when driver is ready
Date: Wed, 27 Jun 2018 12:27:41 +0100	[thread overview]
Message-ID: <20180627112741.GH30628@redhat.com> (raw)
In-Reply-To: <20180627112520.26085-1-pagupta@redhat.com>

On Wed, Jun 27, 2018 at 04:55:20PM +0530, Pankaj Gupta wrote:
>  virtio-rng device causing old guest kernels(2.6.32) to hang on latest qemu.
>  The driver attempts to read from the virtio-rng device too early in it's
>  initialization. Qemu detects guest is not ready and returns, resulting in
>  hang.

Presumably this all worked previously at some point, so do you know what
change in QEMU has caused a regression in this regard.

> 
>  Fix is to handle pending request when guest is running and driver status is
>  set to 'VIRTIO_CONFIG_S_DRIVER_OK'.
> 
> Reported-by: Sergio lopez <slopezpa@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> ---
> v1->v2: Update new status value early only for virtio-rng (Stefan)
> 
>  hw/virtio/virtio-rng.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/hw/virtio/virtio-rng.c b/hw/virtio/virtio-rng.c
> index 289bbcac03..855f1b41d1 100644
> --- a/hw/virtio/virtio-rng.c
> +++ b/hw/virtio/virtio-rng.c
> @@ -156,6 +156,19 @@ static void check_rate_limit(void *opaque)
>      vrng->activate_timer = true;
>  }
>  
> +static void virtio_rng_set_status(VirtIODevice *vdev, uint8_t status)
> +{
> +    VirtIORNG *vrng = VIRTIO_RNG(vdev);
> +
> +    if (!vdev->vm_running) {
> +        return;
> +    }
> +    vdev->status = status;
> +
> +    /* Something changed, try to process buffers */
> +    virtio_rng_process(vrng);
> +}
> +
>  static void virtio_rng_device_realize(DeviceState *dev, Error **errp)
>  {
>      VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> @@ -261,6 +274,7 @@ static void virtio_rng_class_init(ObjectClass *klass, void *data)
>      vdc->realize = virtio_rng_device_realize;
>      vdc->unrealize = virtio_rng_device_unrealize;
>      vdc->get_features = get_features;
> +    vdc->set_status = virtio_rng_set_status;
>  }
>  
>  static const TypeInfo virtio_rng_info = {
> -- 
> 2.14.3
> 
> 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-06-27 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 11:25 [Qemu-devel] [PATCH v2] virtio-rng: process pending requests when driver is ready Pankaj Gupta
2018-06-27 11:27 ` Daniel P. Berrangé [this message]
2018-06-27 12:05   ` Pankaj Gupta
2018-06-29 17:09 ` Stefan Hajnoczi
2018-07-02  5:15   ` Pankaj Gupta

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=20180627112741.GH30628@redhat.com \
    --to=berrange@redhat.com \
    --cc=amit@kernel.org \
    --cc=mst@redhat.com \
    --cc=pagupta@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=slopezpa@redhat.com \
    --cc=stefanha@redhat.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.