From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
intel-gvt-dev@lists.freedesktop.org,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/3] vfio/display: add edid support.
Date: Fri, 22 Feb 2019 06:49:36 +0100 [thread overview]
Message-ID: <20190222054939.19739-1-kraxel@redhat.com> (raw)
The 5.0 linux kernel header update finally landed in master. So this
series has no unmerged dependencies any more. Rebasing and re-sending
for merge.
This series adds EDID support to the qemu vfio display code. Various
display-reladed information -- most importantly the display resolution
which should be used -- is passed to the guest that way. The (initial)
display resolution can be set using the new xres and yres properties.
When supported by the UI it will also be updated on window resizes.
v3:
- change xres+yres property error handling.
- swap one leftover fprintf for a tracepoint.
Gerd Hoffmann (3):
vfio/display: add edid support.
vfio/display: add xres + yres properties
vfio/display: delay link up event
hw/vfio/pci.h | 2 +
include/hw/vfio/vfio-common.h | 4 ++
hw/vfio/display.c | 155 ++++++++++++++++++++++++++++++++++++++++++
hw/vfio/pci.c | 12 ++++
hw/vfio/trace-events | 7 ++
5 files changed, 180 insertions(+)
--
2.9.3
next reply other threads:[~2019-02-22 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 5:49 Gerd Hoffmann [this message]
2019-02-22 5:49 ` [Qemu-devel] [PATCH v3 1/3] vfio/display: add edid support 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
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=20190222054939.19739-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--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).