From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, alsa-devel@alsa-project.org,
jgross@suse.com
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [Xen-devel][PATCH v2 1/3] xen: Introduce shared buffer helpers for page directory...
Date: Tue, 4 Dec 2018 19:28:05 -0500 [thread overview]
Message-ID: <ab1b0d28-f3a1-41ec-82df-2474553dbefe@oracle.com> (raw)
In-Reply-To: <20181130074205.20496-1-andr2000@gmail.com>
On 11/30/18 2:42 AM, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> based frontends. Currently the frontends which implement
> similar code for sharing big buffers between frontend and
> backend are para-virtualized DRM and sound drivers.
> Both define the same way to share grant references of a
> data buffer with the corresponding backend with little
> differences.
>
> Move shared code into a helper module, so there is a single
> implementation of the same functionality for all.
>
> This patch introduces code which is used by sound and display
> frontend drivers without functional changes with the intention
> to remove shared code from the corresponding drivers.
>
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Acked-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
prev parent reply other threads:[~2018-12-05 0:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 7:42 Oleksandr Andrushchenko
2018-11-30 7:42 ` [Xen-devel][PATCH v2 2/3] drm/xen-front: Use Xen common shared buffer implementation Oleksandr Andrushchenko
2018-12-05 8:20 ` Oleksandr Andrushchenko
2018-12-13 10:16 ` Oleksandr Andrushchenko
2018-12-17 10:19 ` Oleksandr Andrushchenko
2018-12-17 14:52 ` [Xen-devel] [PATCH " Boris Ostrovsky
2018-12-17 15:03 ` Oleksandr Andrushchenko
2018-12-17 15:26 ` Boris Ostrovsky
2018-12-18 8:47 ` Oleksandr Andrushchenko
2018-12-18 16:15 ` [Xen-devel][PATCH " Noralf Trønnes
2018-12-18 18:31 ` Boris Ostrovsky
2018-12-18 18:48 ` Oleksandr Andrushchenko
2018-11-30 7:42 ` [Xen-devel][PATCH v2 3/3] ALSA: xen-front: " Oleksandr Andrushchenko
2018-12-03 9:36 ` [alsa-devel] " Takashi Iwai
2018-12-03 9:38 ` Oleksandr Andrushchenko
2018-11-30 7:46 ` [Xen-devel][PATCH v2 1/3] xen: Introduce shared buffer helpers for page directory Oleksandr Andrushchenko
2018-12-05 0:28 ` Boris Ostrovsky [this message]
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=ab1b0d28-f3a1-41ec-82df-2474553dbefe@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=alsa-devel@alsa-project.org \
--cc=andr2000@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--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
all inboxes | Powered by JetHome®