From: davidriley@chromium.org
To: dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org
Cc: David Airlie <airlied@linux.ie>,
Gerd Hoffmann <kraxel@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org,
David Riley <davidriley@chromium.org>
Subject: [PATCH 2/4] drm/virtio: Wake up all waiters when capset response comes in.
Date: Wed, 5 Jun 2019 16:44:21 -0700 [thread overview]
Message-ID: <20190605234423.11348-2-davidriley@chromium.org> (raw)
In-Reply-To: <20190605234423.11348-1-davidriley@chromium.org>
From: David Riley <davidriley@chromium.org>
If multiple callers occur simultaneously, wake them all up.
Signed-off-by: David Riley <davidriley@chromium.org>
---
drivers/gpu/drm/virtio/virtgpu_vq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_vq.c b/drivers/gpu/drm/virtio/virtgpu_vq.c
index e62fe24b1a2e..da71568adb9a 100644
--- a/drivers/gpu/drm/virtio/virtgpu_vq.c
+++ b/drivers/gpu/drm/virtio/virtgpu_vq.c
@@ -588,7 +588,7 @@ static void virtio_gpu_cmd_capset_cb(struct virtio_gpu_device *vgdev,
}
}
spin_unlock(&vgdev->display_info_lock);
- wake_up(&vgdev->resp_wq);
+ wake_up_all(&vgdev->resp_wq);
}
static int virtio_get_edid_block(void *data, u8 *buf,
--
2.22.0.rc1.311.g5d7573a151-goog
next prev parent reply other threads:[~2019-06-05 23:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 23:44 [PATCH 1/4] drm/virtio: Ensure cached capset entries are valid before copying davidriley
2019-06-05 23:44 ` davidriley
2019-06-05 23:44 ` davidriley [this message]
2019-06-05 23:44 ` [PATCH 2/4] drm/virtio: Wake up all waiters when capset response comes in davidriley
2019-06-05 23:44 ` [PATCH 3/4] drm/virtio: Fix cache entry creation race davidriley
2019-06-05 23:44 ` davidriley
2019-06-05 23:44 ` [PATCH 4/4] drm/virtio: Add memory barriers for capset cache davidriley
2019-06-05 23:44 ` davidriley
2019-06-06 7:41 ` Gerd Hoffmann
2019-06-06 7:41 ` Gerd Hoffmann
2019-06-05 23:44 ` davidriley
2019-06-10 21:18 ` [PATCH v2 0/4] drm/virtio: Ensure cached capset entries are valid before copying davidriley
2019-06-10 21:18 ` davidriley
2019-06-10 21:18 ` [PATCH v2 1/4] " davidriley
2019-06-10 21:18 ` davidriley
2019-06-10 21:18 ` [PATCH v2 2/4] drm/virtio: Wake up all waiters when capset response comes in davidriley
2019-06-10 21:18 ` davidriley
2019-06-10 21:18 ` [PATCH v2 3/4] drm/virtio: Fix cache entry creation race davidriley
2019-06-10 21:18 ` davidriley
2019-06-10 21:18 ` [PATCH v2 4/4] drm/virtio: Add memory barriers for capset cache davidriley
2019-06-13 6:59 ` Gerd Hoffmann
2019-06-13 6:59 ` Gerd Hoffmann
2019-06-13 6:59 ` Gerd Hoffmann
2019-06-10 21:18 ` davidriley
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=20190605234423.11348-2-davidriley@chromium.org \
--to=davidriley@chromium.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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.