From: Liam Merwick <liam.merwick@oracle.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
intel-gvt-dev@lists.freedesktop.org,
Liam Merwick <Liam.Merwick@oracle.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/3] vfio/display: delay link up event
Date: Fri, 22 Feb 2019 11:19:11 +0000 [thread overview]
Message-ID: <cd99a2cc-a7e8-ef80-69b3-2082d28a3352@oracle.com> (raw)
In-Reply-To: <20190222054939.19739-4-kraxel@redhat.com>
On 22/02/2019 05:49, Gerd Hoffmann wrote:
> Kick the display link up event with a 0.1 sec delay,
> so the guest has a chance to notice the link down first.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Depending on your thoughts on the suggestion in patch 1 regarding a
comment at the 'err' label - another candidate in
vfio_display_edid_link_up().
Either way:
Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
> ---
> include/hw/vfio/vfio-common.h | 1 +
> hw/vfio/display.c | 26 +++++++++++++++++++++++---
> 2 files changed, 24 insertions(+), 3 deletions(-)
>
> diff --git a/include/hw/vfio/vfio-common.h b/include/hw/vfio/vfio-common.h
> index 5f7f709b95f1..b65a2f051886 100644
> --- a/include/hw/vfio/vfio-common.h
> +++ b/include/hw/vfio/vfio-common.h
> @@ -151,6 +151,7 @@ typedef struct VFIODisplay {
> struct vfio_region_info *edid_info;
> struct vfio_region_gfx_edid *edid_regs;
> uint8_t *edid_blob;
> + QEMUTimer *edid_link_timer;
> struct {
> VFIORegion buffer;
> DisplaySurface *surface;
> diff --git a/hw/vfio/display.c b/hw/vfio/display.c
> index 8bf7c890be96..971e801dc05c 100644
> --- a/hw/vfio/display.c
> +++ b/hw/vfio/display.c
> @@ -38,6 +38,21 @@
> goto err;
>
>
> +static void vfio_display_edid_link_up(void *opaque)
> +{
> + VFIOPCIDevice *vdev = opaque;
> + VFIODisplay *dpy = vdev->dpy;
> + int fd = vdev->vbasedev.fd;
> +
> + dpy->edid_regs->link_state = VFIO_DEVICE_GFX_LINK_STATE_UP;
> + pwrite_field(fd, dpy->edid_info, dpy->edid_regs, link_state);
> + trace_vfio_display_edid_link_up();
> + return;
> +
> +err:
> + trace_vfio_display_edid_write_error();
> +}
> +
> static void vfio_display_edid_update(VFIOPCIDevice *vdev, bool enabled,
> int prefx, int prefy)
> {
> @@ -50,6 +65,7 @@ static void vfio_display_edid_update(VFIOPCIDevice *vdev, bool enabled,
> .prefy = prefy ?: vdev->display_yres,
> };
>
> + timer_del(dpy->edid_link_timer);
> dpy->edid_regs->link_state = VFIO_DEVICE_GFX_LINK_STATE_DOWN;
> pwrite_field(fd, dpy->edid_info, dpy->edid_regs, link_state);
> trace_vfio_display_edid_link_down();
> @@ -77,9 +93,8 @@ static void vfio_display_edid_update(VFIOPCIDevice *vdev, bool enabled,
> goto err;
> }
>
> - dpy->edid_regs->link_state = VFIO_DEVICE_GFX_LINK_STATE_UP;
> - pwrite_field(fd, dpy->edid_info, dpy->edid_regs, link_state);
> - trace_vfio_display_edid_link_up();
> + timer_mod(dpy->edid_link_timer,
> + qemu_clock_get_ms(QEMU_CLOCK_REALTIME) + 100);
> return;
>
> err:
> @@ -136,6 +151,9 @@ static void vfio_display_edid_init(VFIOPCIDevice *vdev)
> vdev->display_yres = dpy->edid_regs->max_yres;
> }
>
> + dpy->edid_link_timer = timer_new_ms(QEMU_CLOCK_REALTIME,
> + vfio_display_edid_link_up, vdev);
> +
> vfio_display_edid_update(vdev, true, 0, 0);
> return;
>
> @@ -154,6 +172,8 @@ static void vfio_display_edid_exit(VFIODisplay *dpy)
>
> g_free(dpy->edid_regs);
> g_free(dpy->edid_blob);
> + timer_del(dpy->edid_link_timer);
> + timer_free(dpy->edid_link_timer);
> }
>
> static void vfio_display_update_cursor(VFIODMABuf *dmabuf,
>
next prev parent reply other threads:[~2019-02-22 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 5:49 [Qemu-devel] [PATCH v3 0/3] vfio/display: add edid support Gerd Hoffmann
2019-02-22 5:49 ` [Qemu-devel] [PATCH v3 1/3] " Gerd Hoffmann
2019-02-22 11:09 ` Liam Merwick
2019-03-08 21:14 ` Alex Williamson
2019-03-11 6:28 ` Gerd Hoffmann
2019-02-22 5:49 ` [Qemu-devel] [PATCH v3 2/3] vfio/display: add xres + yres properties Gerd Hoffmann
2019-02-22 11:13 ` Liam Merwick
2019-02-22 5:49 ` [Qemu-devel] [PATCH v3 3/3] vfio/display: delay link up event Gerd Hoffmann
2019-02-22 11:19 ` Liam Merwick [this message]
2019-03-08 21:16 ` Alex Williamson
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=cd99a2cc-a7e8-ef80-69b3-2082d28a3352@oracle.com \
--to=liam.merwick@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).