From: Gerd Hoffmann <kraxel@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>,
"Zhang, Tina" <tina.zhang@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"Wang, Zhi A" <zhi.a.wang@intel.com>
Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation
Date: Fri, 14 Jul 2017 14:05:39 +0200 [thread overview]
Message-ID: <1500033939.28252.16.camel@redhat.com> (raw)
In-Reply-To: <2c07d8ee-d974-33ec-2cf4-b320fc466c88@nvidia.com>
Hi,
> There could be only two planes, one DRM_PLANE_TYPE_PRIMARY and one
> DRM_PLANE_TYPE_CURSOR.
> Steps from gfx_update for region case would be:
> - VFIO_DEVICE_QUERY_GFX_PLANE with plane_type =
> DRM_PLANE_TYPE_PRIMARY
> - if vfio_device_gfx_plane_info.size > 0, read region for primary
> surface and update console surface
Why? I suspect you want notify the caller whenever the surface has
been updated or not? If so we should add an explicit flag or field for
that.
cheers,
Gerd
next prev parent reply other threads:[~2017-07-14 12:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 22:29 [PATCH v10] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-07-06 14:01 ` Kirti Wankhede
2017-07-11 6:14 ` Gerd Hoffmann
2017-07-11 9:12 ` Daniel Vetter
2017-07-12 2:31 ` Zhang, Tina
2017-07-12 7:40 ` Daniel Vetter
2017-07-12 12:45 ` Kirti Wankhede
2017-07-14 1:30 ` Zhang, Tina
2017-07-14 10:12 ` Kirti Wankhede
2017-07-14 12:05 ` Gerd Hoffmann [this message]
2017-07-14 12:15 ` Kirti Wankhede
2017-07-17 11:03 ` Gerd Hoffmann
2017-07-19 0:16 ` Zhang, Tina
2017-07-19 6:25 ` Gerd Hoffmann
2017-07-19 11:52 ` Kirti Wankhede
2017-07-14 10:01 ` Gerd Hoffmann
2017-07-14 10:15 ` Kirti Wankhede
2017-07-14 12:01 ` Gerd Hoffmann
2017-07-12 3:17 ` Zhenyu Wang
2017-07-12 2:20 ` Zhang, Tina
2017-07-11 6:07 ` Gerd Hoffmann
2017-07-12 2:43 ` Zhang, Tina
2017-07-11 9:15 ` Daniel Vetter
2017-07-12 3:12 ` Zhang, Tina
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=1500033939.28252.16.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tina.zhang@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
--cc=zhiyuan.lv@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