All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: "al1img ." <al1img@gmail.com>
Cc: Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
	Oleksandr Grytsov <oleksandr_grytsov@epam.com>,
	Oleksandr Andrushchenko <andr2000@gmail.com>
Subject: Re: [PATCH v1 0/2] libxl: add PV display device driver interface
Date: Wed, 5 Apr 2017 14:49:26 +0100	[thread overview]
Message-ID: <22756.62950.120863.500360@mariner.uk.xensource.com> (raw)
In-Reply-To: <CACvf2oW_B_cOCcQAOHhaXepECK3okkRPfsX6Thw0eKgEd0CZ_g@mail.gmail.com>

al1img . writes ("Re: [PATCH v1 0/2] libxl: add PV display device driver interface"):
> On Wed, Apr 5, 2017 at 2:05 PM, Ian Jackson <ian.jackson@eu.citrix.com> wrote:
> > Sorry to show my ignorance, but what is a "PV display device" ?
> > Where is the backend ?  What protocol do the frontend/backend speak ?
> 
> This is PV display device which provides virtual screens for frontends.
> We are working on the backend and frontend. They are currently under
> development.

Thanks for the reference to
   http://marc.info/?l=xen-devel&m=149137266022490&w=2
which was very helpful.

I think you should combine this series with that patch.  That patch
will need wider review and ack from Konrad (as our PV interface tsar);
AFAICT you're working on that, but I would like to be CC'd on the
mails too.

> > What are the parameters ?
> 
> It has two parameters:
>     * backend - specifies domain where the backend is running;
>     * beAlloc - indicated where display buffers should be allocated
> (see Backend buffer allocation in [3]);

I don't understand that, I'm afraid.  I guess what I'm missing in this
area is: the guest sees a virtual display device.  But how is this
presented/accessed/named/whatever on the host ?  I would expect to see
some configuraton for this in the libxl idl.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-04-05 13:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 10:03 [PATCH v1 0/2] libxl: add PV display device driver interface Oleksandr Grytsov
2017-04-05 10:03 ` [PATCH v1 1/2] " Oleksandr Grytsov
2017-04-05 10:03 ` [PATCH v1 2/2] xl: add PV display device commands Oleksandr Grytsov
2017-04-05 11:05 ` [PATCH v1 0/2] libxl: add PV display device driver interface Ian Jackson
2017-04-05 12:25   ` al1img .
2017-04-05 13:49     ` Ian Jackson [this message]
2017-04-05 14:00       ` Konrad Rzeszutek Wilk
2017-04-05 14:18         ` Oleksandr Grytsov
2017-04-05 14:28           ` Oleksandr Grytsov
2017-04-05 14:28           ` Ian Jackson
2017-04-05 14:53             ` Oleksandr Grytsov
2017-04-05 15:50               ` Ian Jackson
2017-04-06  9:22                 ` Oleksandr Grytsov
2017-04-06 11:17                   ` Ian Jackson
2017-04-06 12:42                     ` Oleksandr Grytsov
2017-04-06 13:03                       ` Ian Jackson
2017-04-06 13:27                         ` Oleksandr Grytsov
2017-04-10 10:58                           ` Oleksandr Grytsov
2017-04-12 16:48                             ` Wei Liu
2017-04-13  8:41                               ` Oleksandr Grytsov
2017-04-13 12:54                             ` Ian Jackson
2017-04-14 10:12                               ` Oleksandr Grytsov
2017-04-26 10:15                                 ` Oleksandr Grytsov
2017-05-02 14:28                                 ` Ian Jackson
2017-05-03 15:08                                   ` Oleksandr Grytsov
2017-05-03 15:13                                     ` Ian Jackson
2017-05-04  8:49                                       ` Oleksandr Grytsov
2017-05-12 12:12                                         ` Oleksandr Grytsov
2017-05-18 11:42                                           ` Oleksandr Grytsov

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=22756.62950.120863.500360@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=al1img@gmail.com \
    --cc=andr2000@gmail.com \
    --cc=jgross@suse.com \
    --cc=oleksandr_grytsov@epam.com \
    --cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.