From: Gerd Hoffmann <kraxel@redhat.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
intel-gvt-dev@lists.freedesktop.org,
open list <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] vfio: add edid api for display (vgpu) devices.
Date: Mon, 17 Sep 2018 10:50:33 +0200 [thread overview]
Message-ID: <20180917085033.ttcs3cpznnf3wngd@sirius.home.kraxel.org> (raw)
In-Reply-To: <20180917065154.GI20737@zhen-hp.sh.intel.com>
> > +#define VFIO_DEVICE_INFO_CAP_EDID 1
> > +
> > +struct vfio_device_info_edid_cap {
> > + struct vfio_info_cap_header header;
> > + __u32 max_x; /* Max display height (zero == no limit) */
> > + __u32 max_y; /* Max display height (zero == no limit) */
> > +};
>
> As current virtual display for Intel vGPU is still emulating against real HW
> pipeline with same limitations, asked display developers that whether or not
> specific mode can work might still depend on current or future HW behavior.
> So could we add some hints on what kind of edid mode vfio device can operate?
> Some may support arbitrary modes, but some may only support standard modes.
What kind of restrictions do we have here? Really to a fixed list of
standard modes?
Some testing (kaby lake) indicates y axis has no restrictions and x axis
gets rounded up to the next multiple of 8 pixels (32 bytes), maybe to
align scanlines with cachelines?
Oh, and btw: Seems the resolution restriction (to 1024x768 for the
smallest vgpu type) seems to not be enforced. Intentional?
cheers,
Gerd
next prev parent reply other threads:[~2018-09-17 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180913054745.6353-1-kraxel@redhat.com>
2018-09-13 5:47 ` [PATCH 1/2] vfio: add edid api for display (vgpu) devices Gerd Hoffmann
2018-09-13 17:51 ` Alex Williamson
2018-09-14 12:25 ` Gerd Hoffmann
2018-09-14 15:31 ` Alex Williamson
2018-09-17 6:51 ` Zhenyu Wang
2018-09-17 8:50 ` Gerd Hoffmann [this message]
2018-09-17 9:15 ` Zhenyu Wang
2018-09-17 10:13 ` Gerd Hoffmann
2018-09-13 5:47 ` [PATCH 2/2] vfio: add edid support to mbochs sample driver Gerd Hoffmann
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=20180917085033.ttcs3cpznnf3wngd@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyuw@linux.intel.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 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).