From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello!
Notes.
1. Boris, I put your R-b tag as I almost didn't change Xen part
of the driver (see below). Please let me know if this is not acceptable,
so I remove the tag.
2. With this patch series I am also adding a patc
Vetter <daniel.vet...@ffwll.ch>
Signed-off-by: Noralf Trønnes <nor...@tronnes.org>
Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Tested-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Cc: intel-...@lists.freedesktop.org
---
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user-space application
and its helper library [2], capable of running as a Weston client
or DRM master.
Configuration o
On 03/27/2018 12:50 PM, Daniel Vetter wrote:
On Tue, Mar 27, 2018 at 11:34 AM, Oleksandr Andrushchenko
<andr2...@gmail.com> wrote:
Hi, Daniel!
On 03/26/2018 03:46 PM, Oleksandr Andrushchenko wrote:
On 03/26/2018 11:18 AM, Daniel Vetter wrote:
On Fri, Mar 23, 2018 at 05:54:49PM
Hi, Daniel!
On 03/26/2018 03:46 PM, Oleksandr Andrushchenko wrote:
On 03/26/2018 11:18 AM, Daniel Vetter wrote:
On Fri, Mar 23, 2018 at 05:54:49PM +0200, Oleksandr Andrushchenko wrote:
My apologies, but I found a few more things that look strange and
should
be cleaned up. Sorry
Hi, Konrad!
Could you please review?
Thank you,
Oleksandr
On 03/21/2018 09:25 AM, Oleksandr Andrushchenko wrote:
On 03/21/2018 09:20 AM, Takashi Iwai wrote:
On Wed, 21 Mar 2018 08:15:36 +0100,
Oleksandr Andrushchenko wrote:
On 03/20/2018 10:22 PM, Takashi Iwai wrote:
On Mon, 19 Mar 2018 08
On 03/26/2018 11:18 AM, Daniel Vetter wrote:
On Fri, Mar 23, 2018 at 05:54:49PM +0200, Oleksandr Andrushchenko wrote:
My apologies, but I found a few more things that look strange and should
be cleaned up. Sorry for this iterative review approach, but I think we're
slowly getting there.
Thank
My apologies, but I found a few more things that look strange and should
be cleaned up. Sorry for this iterative review approach, but I think we're
slowly getting there.
Thank you for reviewing!
Cheers, Daniel
---
+static int xen_drm_drv_dumb_create(struct drm_file *filp,
+
On 03/22/2018 03:14 AM, Boris Ostrovsky wrote:
On 03/21/2018 10:58 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user-space application
and its helper library [2], capable of running as a Weston client
or DRM master.
Configuration o
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello!
This patch series adds support for Xen [1] para-virtualized
frontend display driver. It implements the protocol from
include/xen/interface/io/displif.h [2].
Accompanying backend [3] is implemented as a user-space appli
On 03/20/2018 03:47 PM, Daniel Vetter wrote:
On Tue, Mar 20, 2018 at 01:58:01PM +0200, Oleksandr Andrushchenko wrote:
On 03/19/2018 05:28 PM, Daniel Vetter wrote:
There should be no difference between immediate removal and delayed
removal of the drm_device from the xenbus pov. The lifetimes
On 03/21/2018 09:20 AM, Takashi Iwai wrote:
On Wed, 21 Mar 2018 08:15:36 +0100,
Oleksandr Andrushchenko wrote:
On 03/20/2018 10:22 PM, Takashi Iwai wrote:
On Mon, 19 Mar 2018 08:22:19 +0100,
Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
On 03/20/2018 10:22 PM, Takashi Iwai wrote:
On Mon, 19 Mar 2018 08:22:19 +0100,
Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello, all!
In order to provide explicit synchronization between backend and
frontend the following c
On 03/19/2018 05:28 PM, Daniel Vetter wrote:
On Mon, Mar 19, 2018 at 3:19 PM, Oleksandr Andrushchenko
<andr2...@gmail.com> wrote:
On 03/19/2018 03:51 PM, Daniel Vetter wrote:
On Fri, Mar 16, 2018 at 12:52:09PM +0200, Oleksandr Andrushchenko wrote:
Hi, Daniel!
Sorry, if I strip the pat
On 03/20/2018 01:23 AM, Boris Ostrovsky wrote:
On 03/13/2018 12:21 PM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello!
Resending with all the patches squashed on Daniel's request.
Which of the two series are we supposed to review?
On 03/19/2018 03:51 PM, Daniel Vetter wrote:
On Fri, Mar 16, 2018 at 12:52:09PM +0200, Oleksandr Andrushchenko wrote:
Hi, Daniel!
Sorry, if I strip the patch too much below.
On 03/16/2018 10:23 AM, Daniel Vetter wrote:
S-o-b line went missing here :-)
will restore it back ;)
I've read
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
In order to provide explicit synchronization between backend and
frontend the following changes are introduced in the protocol:
- add new ring buffer for sending asynchronous events from
backend to frontend to report
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Extend the size of the requests and responses to 64 octets.
Bump protocol version to 2.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
---
xen/include/public/io/sndif.h | 22 +++--
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
In order to provide explicit stream parameter negotiation between
backend and frontend the following change is introduced to the protocol:
- add XENSND_OP_HW_PARAM_QUERY request to read/update
stream configuration space: r
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Some of the request descriptions have "reserved" fields
missed: fix this by adding corresponidng entries.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
---
xen/include/public/io/sn
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Protocol version was referenced in the protocol description,
but missed its definition. Fix this by adding a constant
for current protocol version.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com&
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello, all!
In order to provide explicit synchronization between backend and
frontend the following changes are introduced in the protocol:
- bump protocol version to 2
- add new ring buffer for sending asynchronous event
Hi, Daniel!
Sorry, if I strip the patch too much below.
On 03/16/2018 10:23 AM, Daniel Vetter wrote:
S-o-b line went missing here :-)
will restore it back ;)
I've read through it, 2 actual review comments (around hot-unplug and
around the error recovery for failed flips), a few bikesheds,
On 03/15/2018 10:17 PM, Konrad Rzeszutek Wilk wrote:
+ **
+ *Back to front events delivery
+ **
+ * In order to deliver
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
In order to provide explicit synchronization between backend and
frontend the following changes are introduced in the protocol:
- bump protocol version to 2
- add new ring buffer for sending asynchronous events from
b
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Protocol version was referenced in the protocol description,
but missed its definition. Fix this by adding a constant
for current protocol version.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com&
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
In order to provide explicit stream parameter negotiation between
backend and frontend the following changes are introduced in the protocol:
add XENSND_OP_HW_PARAM_QUERY request to read/update
configuration space for the par
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello, all!
In order to provide explicit synchronization between backend and
frontend the following changes are introduced in the protocol:
- bump protocol version to 2
- add new ring buffer for sending asynchronous event
On 03/13/2018 08:48 PM, Takashi Iwai wrote:
On Tue, 13 Mar 2018 18:31:55 +0100,
Oleksandr Andrushchenko wrote:
On 03/13/2018 06:31 PM, Takashi Iwai wrote:
On Tue, 13 Mar 2018 12:49:00 +0100,
Oleksandr Andrushchenko wrote:
So, I tried to make a POC to stress the protocol changes and see
what
On 03/13/2018 06:31 PM, Takashi Iwai wrote:
On Tue, 13 Mar 2018 12:49:00 +0100,
Oleksandr Andrushchenko wrote:
So, I tried to make a POC to stress the protocol changes and see
what implementation of the HW parameter negotiation would look like.
Please find protocol changes at [1]:
- add
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user-space application
and its helper library [2], capable of running as a Weston client
or DRM master.
Configuration o
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello!
Resending with all the patches squashed on Daniel's request.
This patch series adds support for Xen [1] para-virtualized
frontend display driver. It implements the protocol from
include/xen/interface/io/displi
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Provide kernel documentation for the Xen para-virtualized
frontend DRM driver.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
---
Documentation/gpu/index.rst | 1 +
Documentation/gpu/x
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello!
This patch series adds support for Xen [1] para-virtualized
frontend display driver. It implements the protocol from
include/xen/interface/io/displif.h [2].
Accompanying backend [3] is implemented as a user-space appli
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Read configuration values from Xen store according
to xen/interface/io/displif.h protocol:
- read connector(s) configuration
- read buffer allocation mode (backend/frontend)
Signed-off-by: Oleksandr Andrush
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Initial handling for Xen bus states: implement
Xen bus state machine for the frontend driver according to
the state diagram and recovery flow from display para-virtualized
protocol: xen/interface/io/displif.h.
Sign
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement GEM handling depending on driver mode of operation:
depending on the requirements for the para-virtualized environment, namely
requirements dictated by the accompanying DRM/(v)GPU drivers running in both
host and
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Handle Xen event channels:
- create for all configured connectors and publish
corresponding ring references and event channels in Xen store,
so backend can connect
- implement event channels interrupt handlers
-
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement shared buffer handling according to the
para-virtualized display device protocol at xen/interface/io/displif.h:
- handle page directories according to displif protocol:
- allocate and share page direc
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Introduce skeleton of the para-virtualized Xen display
frontend driver. This patch only adds required
essential stubs.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
---
drivers/gpu
Hi,
On 03/12/2018 08:26 AM, Oleksandr Andrushchenko wrote:
On 03/11/2018 10:15 AM, Takashi Iwai wrote:
Hi,
sorry for the long latency.
Hi, no problem, thank you
On Wed, 07 Mar 2018 09:49:24 +0100,
Oleksandr Andrushchenko wrote:
Suppose that we negotiate from the frontend to the backend
On 03/11/2018 10:15 AM, Takashi Iwai wrote:
Hi,
sorry for the long latency.
Hi, no problem, thank you
On Wed, 07 Mar 2018 09:49:24 +0100,
Oleksandr Andrushchenko wrote:
Suppose that we negotiate from the frontend to the backend like
int query_hw_param(int parm, int *min_p, int
On 03/06/2018 06:30 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 17:04:41 +0100,
Oleksandr Andrushchenko wrote:
If we decide to negotiate the parameters, then it can't be done
at .open stage as well, as at this moment we don't know stream
parameters yet, e.g. we don't know the number of channels
On 03/06/2018 05:06 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 15:48:53 +0100,
Oleksandr Andrushchenko wrote:
And, now an open question for XEN comes: what kind of restriction
should be applied to the frontend. Obviously it depends on the
backend, so there must be some communication
On 03/06/2018 04:27 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 15:13:13 +0100,
Oleksandr Andrushchenko wrote:
On 03/06/2018 03:48 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 14:30:05 +0100,
Oleksandr Andrushchenko wrote:
On 03/06/2018 02:52 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 13:05
On 03/06/2018 03:48 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 14:30:05 +0100,
Oleksandr Andrushchenko wrote:
On 03/06/2018 02:52 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 13:05:16 +0100,
Oleksandr Andrushchenko wrote:
On 03/06/2018 01:32 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 12:25
On 03/06/2018 02:52 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 13:05:16 +0100,
Oleksandr Andrushchenko wrote:
On 03/06/2018 01:32 PM, Takashi Iwai wrote:
On Tue, 06 Mar 2018 12:25:07 +0100,
Oleksandr Andrushchenko wrote:
On 03/06/2018 12:52 PM, Takashi Iwai wrote:
On Mon, 05 Feb 2018 09:24
On 03/06/2018 12:52 PM, Takashi Iwai wrote:
On Mon, 05 Feb 2018 09:24:58 +0100,
Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hi, all!
Foreword
This change is aimed to add support for explicit back and front
synchronization
On 03/05/2018 11:32 AM, Daniel Vetter wrote:
On Wed, Feb 21, 2018 at 10:03:41AM +0200, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement GEM handling depending on driver mode of operation:
depending on the requirements for th
On 03/05/2018 11:23 AM, Daniel Vetter wrote:
On Wed, Feb 21, 2018 at 10:03:40AM +0200, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement kernel modesetiing/connector handling using
DRM simple KMS helper pipeline:
- implement KM
On 03/05/2018 11:25 AM, Daniel Vetter wrote:
On Wed, Feb 21, 2018 at 10:03:42AM +0200, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Handle communication with the backend:
- send requests and wait for the responses acc
On 03/05/2018 11:13 AM, Daniel Vetter wrote:
On Wed, Feb 21, 2018 at 10:03:39AM +0200, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement essential initialization of the display driver:
- introduce required data structures
-
Any chance ALSA community may also review the below?
BTW, the driver, with the changes proposed, is at [1]
Thank you,
Oleksandr
On 02/05/2018 10:24 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hi, all!
Foreword
This
On 03/02/2018 12:11 AM, Konrad Rzeszutek Wilk wrote:
* +++++
* | gref_directory | 24
* +++++
- * |
s,
Gerd
Thank you,
Oleksandr Andrushchenko
[1] https://www.youtube.com/watch?v=FcVDHBQInxA
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Hello,
Konrad, Takashi, Takashi and Clemens!
Could you please take a look at this series if it meets
ALSA expectations on para-virtualized sound for Xen?
Thank you,
Oleksandr
On 02/05/2018 10:24 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.
On 02/28/2018 09:46 PM, Boris Ostrovsky wrote:
On 02/27/2018 01:52 AM, Oleksandr Andrushchenko wrote:
On 02/27/2018 01:47 AM, Boris Ostrovsky wrote:
On 02/23/2018 10:35 AM, Oleksandr Andrushchenko wrote:
On 02/23/2018 05:26 PM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr
QEMU to run.
Although this use case would work on x86 it will require additional changes
to get this running on ARM, which is my target platform.
Thank you,
Oleksandr
On 02/26/2018 10:21 AM, Oleksandr Andrushchenko wrote:
**
*Hi, all!*
*
Last *Friday* some concerns on #dri-devel were raised
On 02/27/2018 01:47 AM, Boris Ostrovsky wrote:
On 02/23/2018 10:35 AM, Oleksandr Andrushchenko wrote:
On 02/23/2018 05:26 PM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+static struct xen_gem_object *gem_create(struct drm_device *dev,
size_t size
ckend which supports multi-touch and guest
display(s) and running either as a weston client (which is not supported
by QEMU at the moment?) or KMS/DRM client. This allows us to enable much
more use-cases**without the need to run QEMU.
*
*Thank you,*
**Oleksandr Andrushchenko*
*
*
*
*[1]
On 02/23/2018 05:26 PM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+static struct xen_gem_object *gem_create(struct drm_device *dev, size_t size)
+{
+ struct xen_drm_front_drm_info *drm_info = dev->dev_private;
+ struct xen_gem_object *xen_
On 02/23/2018 05:12 PM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+
+struct drm_driver xen_drm_driver = {
+ .driver_features = DRIVER_GEM | DRIVER_MODESET |
+DRIVER_PRIME | DRIVER_ATOMIC,
+ .lastclose
On 02/23/2018 04:39 PM, Boris Ostrovsky wrote:
On 02/23/2018 01:37 AM, Oleksandr Andrushchenko wrote:
On 02/23/2018 12:23 AM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+static struct xenbus_driver xen_driver = {
+.ids = xen_drv_ids,
+.probe
On 02/23/2018 04:44 PM, Boris Ostrovsky wrote:
On 02/23/2018 02:00 AM, Oleksandr Andrushchenko wrote:
On 02/23/2018 01:50 AM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+
+static irqreturn_t evtchnl_interrupt_ctrl(int irq, void *dev_id)
+{
+struct
On 02/23/2018 04:36 PM, Boris Ostrovsky wrote:
On 02/23/2018 02:53 AM, Oleksandr Andrushchenko wrote:
On 02/23/2018 02:25 AM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
static int __init xen_drv_init(void)
{
+/* At the moment we only support case
On 02/23/2018 01:50 AM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+
+static irqreturn_t evtchnl_interrupt_ctrl(int irq, void *dev_id)
+{
+ struct xen_drm_front_evtchnl *evtchnl = dev_id;
+ struct xen_drm_front_info *front_info = evtchnl
On 02/23/2018 01:20 AM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+
+static int cfg_connector(struct xen_drm_front_info *front_info,
+ struct xen_drm_front_cfg_connector *connector,
+ const char *path, int index)
+{
+ char
On 02/23/2018 12:23 AM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+static struct xenbus_driver xen_driver = {
+ .ids = xen_drv_ids,
+ .probe = xen_drv_probe,
+ .remove = xen_drv_remove,
+ .otherend_changed = backend_on_changed,
What
On 02/21/2018 12:19 PM, Roger Pau Monné wrote:
On Wed, Feb 21, 2018 at 11:42:23AM +0200, Oleksandr Andrushchenko wrote:
On 02/21/2018 11:17 AM, Roger Pau Monné wrote:
On Wed, Feb 21, 2018 at 10:03:34AM +0200, Oleksandr Andrushchenko wrote:
--- /dev/null
+++ b/drivers/gpu/drm/xen
On 02/21/2018 11:17 AM, Roger Pau Monné wrote:
On Wed, Feb 21, 2018 at 10:03:34AM +0200, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Introduce skeleton of the para-virtualized Xen display
frontend driver. This patch only adds re
On 02/21/2018 11:09 AM, Juergen Gross wrote:
On 21/02/18 09:47, Oleksandr Andrushchenko wrote:
On 02/21/2018 10:19 AM, Juergen Gross wrote:
On 21/02/18 09:03, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Introduce skeleton of th
On 02/21/2018 10:23 AM, Juergen Gross wrote:
On 21/02/18 09:03, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Initial handling for Xen bus states: implement
Xen bus state machine for the frontend driver according to
the state d
On 02/21/2018 10:19 AM, Juergen Gross wrote:
On 21/02/18 09:03, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Introduce skeleton of the para-virtualized Xen display
frontend driver. This patch only adds required
essential stubs.
Sign
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement essential initialization of the display driver:
- introduce required data structures
- handle DRM/KMS driver registration
- perform basic DRM driver initialization
- register driver on backend connection
-
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement kernel modesetiing/connector handling using
DRM simple KMS helper pipeline:
- implement KMS part of the driver with the help of DRM
simple pipepline helper which is possible due to the fact
that the para-virtu
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Introduce skeleton of the para-virtualized Xen display
frontend driver. This patch only adds required
essential stubs.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
---
drivers/gpu
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Read configuration values from Xen store according
to xen/interface/io/displif.h protocol:
- read connector(s) configuration
- read buffer allocation mode (backend/frontend)
Signed-off-by: Oleksandr Andrush
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement shared buffer handling according to the
para-virtualized display device protocol at xen/interface/io/displif.h:
- handle page directories according to displif protocol:
- allocate and share page direc
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Implement GEM handling depending on driver mode of operation:
depending on the requirements for the para-virtualized environment, namely
requirements dictated by the accompanying DRM/(v)GPU drivers running in both
host and
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Handle communication with the backend:
- send requests and wait for the responses according
to the displif protocol
- serialize access to the communication channel
- time-out used for backend communication is set to 3
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Initial handling for Xen bus states: implement
Xen bus state machine for the frontend driver according to
the state diagram and recovery flow from display para-virtualized
protocol: xen/interface/io/displif.h.
Sign
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Handle Xen event channels:
- create for all configured connectors and publish
corresponding ring references and event channels in Xen store,
so backend can connect
- implement event channels interrupt handlers
-
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hello!
This patch series adds support for Xen [1] para-virtualized
frontend display driver. It implements the protocol from
include/xen/interface/io/displif.h [2].
Accompanying backend [3] is implemented as a user-space appli
ping
On 02/05/2018 10:24 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hi, all!
Foreword
This change is aimed to add support for explicit back and front
synchronization during playback and capture in response to comments
On 02/06/2018 02:52 PM, Wei Liu wrote:
On Tue, Feb 06, 2018 at 02:44:56PM +0200, Oleksandr Andrushchenko wrote:
From aa1f20af73a5a3c8f2c904b857a79334d18d41ff Mon Sep 17 00:00:00 2001
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Date: Wed, 20 Dec 2017 17:51:18
Hi, Wei!
On 02/06/2018 02:36 PM, Wei Liu wrote:
On Wed, Dec 20, 2017 at 06:27:02PM +0200, Oleksandr Andrushchenko wrote:
Hi, all!
While trying to reboot a domain which has iomem configured
(we are passing through some devices), I found an issue,
that after domain reboot those iomem's
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
In order to provide explicit synchronization between backend and
frontend the following changes are introduced in the protocol:
- add new ring buffer for sending asynchronous events from
backend to frontend to report
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Protocol version was referenced in the protocol description,
but missed its definition. Fix this by adding a constant
for current protocol version.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com&
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hi, all!
Foreword
This change is aimed to add support for explicit back and front
synchronization during playback and capture in response to comments
raised during upstream attempt of the para-virtualized sound fr
On 02/02/2018 10:54 AM, Eduardo Otubo wrote:
On Wed, Jan 31, 2018 at 05:00:23PM +0200, Oleksandr Andrushchenko wrote:
Hi, Eduardo!
I am working on a frontend driver (PV DRM) and also seeing some strange
things on driver unloading:
xt# rmmod -f drm_xen_front.ko
[ 3236.462497] [drm
On 02/01/2018 11:09 PM, Boris Ostrovsky wrote:
On 02/01/2018 03:24 PM, Oleksandr Andrushchenko wrote:
On 02/01/2018 10:08 PM, Boris Ostrovsky wrote:
On 02/01/2018 03:57 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Current
On 02/01/2018 10:08 PM, Boris Ostrovsky wrote:
On 02/01/2018 03:57 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Current xenbus frontend driver removal flow first disconnects
the driver from xenbus and then calls driver's remove ca
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Hi, all!
While working on DRM PV frontend driver I faced an issue with
driver removal, e.g. when driver's .remove callback is called
the driver is already disconnected form the xenbus and it is not
possible to synch
Ian, Wei,
could you please take a look at the below?
Thank you,
Oleksandr
On 12/20/2017 06:27 PM, Oleksandr Andrushchenko wrote:
Hi, all!
While trying to reboot a domain which has iomem configured
(we are passing through some devices), I found an issue,
that after domain reboot those
Hi, Eduardo!
I am working on a frontend driver (PV DRM) and also seeing some strange
things on driver unloading:
xt# rmmod -f drm_xen_front.ko
[ 3236.462497] [drm] Unregistering XEN PV vdispl
[ 3236.485745] [drm:xen_drv_remove [drm_xen_front]] *ERROR* Backend
state is InitWait while removing
From: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Some user-space applications expect multi-touch pressure
on contact to be reported if it is advertised in device
properties. Otherwise, such applications may treat reports
not as actual touches, but hovering. Currently this i
On 12/22/2017 05:58 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Dec 22, 2017 at 05:48:45PM +0200, Oleksandr Andrushchenko wrote:
On 12/22/2017 05:12 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Dec 11, 2017 at 10:45:27AM +0200, Oleksandr Andrushchenko wrote:
ping
..snip..
This is implemented
On 12/22/2017 05:12 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Dec 11, 2017 at 10:45:27AM +0200, Oleksandr Andrushchenko wrote:
ping
..snip..
This is implemented as a change to the sndif protocol [8] and allows
[8]
https://github.com/andr2000/linux/commit
On 12/20/2017 01:27 AM, Dongwon Kim wrote:
This patch series contains the implementation of a new device driver,
hyper_dmabuf, which provides a method for DMA-BUF sharing across
different OSes running on the same virtual OS platform powered by
a hypervisor.
This is very interesting at least in
1301 - 1400 of 1401 matches
Mail list logo
