From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
To: "Jürgen Groß" <jgross@suse.com>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>
Cc: Oleksandr Andrushchenko <andr2000@gmail.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 0/5] Fixes and improvements for Xen pvdrm
Date: Thu, 13 Aug 2020 07:21:56 +0000 [thread overview]
Message-ID: <b4069b96-477b-e507-e20c-9cb25376c40d@epam.com> (raw)
In-Reply-To: <231ee1e7-c2fa-3c2a-f444-f9f813fc906d@suse.com>
On 8/13/20 10:05 AM, Jürgen Groß wrote:
> On 13.08.20 08:32, Oleksandr Andrushchenko wrote:
>> Juergen, Boris,
>>
>> can we please merge these via Xen Linux tree as I have collected enough Ack/R-b?
>>
>> The series has DRM patches, but those anyway are Xen related, so I think
>>
>> this should be fine from DRI point of view.
>
> Yes, fine with me.
Great, thank you
>
>
> Juergen
>
>>
>> Thank you,
>>
>> Oleksandr
>>
>> On 8/13/20 9:21 AM, Oleksandr Andrushchenko wrote:
>>> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>>
>>> Hello,
>>>
>>> This series contains an assorted set of fixes and improvements for
>>> the Xen para-virtualized display driver and grant device driver which
>>> I have collected over the last couple of months:
>>>
>>> 1. Minor fixes to grant device driver and drm/xen-front.
>>>
>>> 2. New format (YUYV) added to the list of the PV DRM supported formats
>>> which allows the driver to be used in zero-copying use-cases when
>>> a camera device is the source of the dma-bufs.
>>>
>>> 3. Synchronization with the latest para-virtualized protocol definition
>>> in Xen [1].
>>>
>>> 4. SGT offset is now propagated to the backend: while importing a dmabuf
>>> it is possible that the data of the buffer is put with offset which is
>>> indicated by the SGT offset. This is needed for some GPUs which have
>>> non-zero offset.
>>>
>>> Thank you,
>>> Oleksandr Andrushchenko
>>>
>>> [1] https://urldefense.com/v3/__https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=c27a184225eab54d20435c8cab5ad0ef384dc2c0__;!!GF_29dbcQIUBPA!iAHOdk4M167VNM1AypMGVmyKJu-iqC9e5cXyu6N595Np3iyIZDnZl0MIBX3IROJSD1GSMX_GfQ$ [xenbits[.]xen[.]org]
>>>
>>> Changes since v1:
>>> =================
>>>
>>> 1. Removed patch which adds EDID to PV DRM as it needs more time for review:
>>> "5. Version 2 of the Xen displif protocol adds XENDISPL_OP_GET_EDID
>>> request which allows frontends to request EDID structure per
>>> connector. This request is optional and if not supported by the
>>> backend then visible area is still defined by the relevant
>>> XenStore's "resolution" property.
>>> If backend provides EDID with XENDISPL_OP_GET_EDID request then
>>> its values must take precedence over the resolutions defined in
>>> XenStore."
>>> I will send this as a dedicated patch.
>>>
>>> 2. Added missing CC stable for the patches with fixes
>>>
>>> Oleksandr Andrushchenko (5):
>>> xen/gntdev: Fix dmabuf import with non-zero sgt offset
>>> drm/xen-front: Fix misused IS_ERR_OR_NULL checks
>>> drm/xen-front: Add YUYV to supported formats
>>> xen: Sync up with the canonical protocol definition in Xen
>>> drm/xen-front: Pass dumb buffer data offset to the backend
>>>
>>> drivers/gpu/drm/xen/xen_drm_front.c | 10 +--
>>> drivers/gpu/drm/xen/xen_drm_front.h | 2 +-
>>> drivers/gpu/drm/xen/xen_drm_front_conn.c | 1 +
>>> drivers/gpu/drm/xen/xen_drm_front_gem.c | 11 +--
>>> drivers/gpu/drm/xen/xen_drm_front_kms.c | 2 +-
>>> drivers/xen/gntdev-dmabuf.c | 8 +++
>>> include/xen/interface/io/displif.h | 91 +++++++++++++++++++++++-
>>> 7 files changed, 111 insertions(+), 14 deletions(-)
>>>
>>
>
next prev parent reply other threads:[~2020-08-13 7:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 6:21 [PATCH v2 0/5] Fixes and improvements for Xen pvdrm Oleksandr Andrushchenko
2020-08-13 6:21 ` [PATCH v2 1/5] xen/gntdev: Fix dmabuf import with non-zero sgt offset Oleksandr Andrushchenko
2020-08-13 6:21 ` [PATCH v2 2/5] drm/xen-front: Fix misused IS_ERR_OR_NULL checks Oleksandr Andrushchenko
2020-08-13 6:21 ` [PATCH v2 3/5] drm/xen-front: Add YUYV to supported formats Oleksandr Andrushchenko
2020-08-13 6:21 ` [PATCH v2 4/5] xen: Sync up with the canonical protocol definition in Xen Oleksandr Andrushchenko
2020-08-13 6:21 ` [PATCH v2 5/5] drm/xen-front: Pass dumb buffer data offset to the backend Oleksandr Andrushchenko
2020-08-13 6:32 ` [PATCH v2 0/5] Fixes and improvements for Xen pvdrm Oleksandr Andrushchenko
2020-08-13 7:05 ` Jürgen Groß
2020-08-13 7:21 ` Oleksandr Andrushchenko [this message]
2020-08-13 15:02 ` Jürgen Groß
2020-08-13 15:10 ` Oleksandr Andrushchenko
2020-08-13 15:13 ` Jürgen Groß
2020-08-13 16:30 ` Oleksandr Andrushchenko
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=b4069b96-477b-e507-e20c-9cb25376c40d@epam.com \
--to=oleksandr_andrushchenko@epam.com \
--cc=airlied@linux.ie \
--cc=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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