From: Ian Jackson <ian.jackson@citrix.com>
To: Oleksandr Grytsov <al1img@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Oleksandr Grytsov <oleksandr_grytsov@epam.com>,
"wl@xen.org" <wl@xen.org>
Subject: Re: [Xen-devel] [PATCH v1 1/2] libxl: introduce new backend type VINPUT
Date: Fri, 11 Oct 2019 15:58:02 +0100 [thread overview]
Message-ID: <23968.39034.34800.276030@mariner.uk.xensource.com> (raw)
In-Reply-To: <20191008141024.10885-2-al1img@gmail.com>
Oleksandr Grytsov writes ("[PATCH v1 1/2] libxl: introduce new backend type VINPUT"):
> From: Oleksandr Grytsov <oleksandr_grytsov@epam.com>
>
> There are two kind of VKBD devices: with QEMU backend and user space
> backend. In current implementation they can't be distinguished as both use
> VKBD backend type. As result, user space KBD backend is started and
> stopped as QEMU backend. This commit adds new device kind VINPUT to be
> used as backend type for user space KBD backend.
I find this confusing. I'm not sure this change is right. But I'm
afraid the original patches in this area passed me by so I don't know
much about it.
I think it was a48e00f14a2d "libxl: add backend type and id to vkb"
which introduced what you are calling "user space" backends. It
appears that the vkb backend type enum was introduced there
specifically to distinguish between these two situations. For reasons
Am I wrong ? If not, why is this not working or not suitable ?
I also don't understand why the "user space" kbd backend seems to be
"linux" in the enum. Where is the implementation of this user space
backend ? Is it be controlled entirely through xenstore ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-11 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 14:10 [Xen-devel] [PATCH v1 0/2] Remove backend xen store entry on domain destroy Oleksandr Grytsov
2019-10-08 14:10 ` [Xen-devel] [PATCH v1 1/2] libxl: introduce new backend type VINPUT Oleksandr Grytsov
2019-10-11 14:58 ` Ian Jackson [this message]
2019-10-11 15:57 ` Oleksandr Grytsov
2019-10-11 17:03 ` Ian Jackson
2019-10-16 13:26 ` Oleksandr Grytsov
2019-10-28 14:06 ` Oleksandr Grytsov
2019-11-04 14:52 ` Oleksandr Grytsov
2019-11-15 19:43 ` Ian Jackson
2019-11-18 11:40 ` Oleksandr Grytsov
2019-11-18 17:48 ` Ian Jackson
2019-11-18 17:55 ` [Xen-devel] [PATCH for-4.13 " Ian Jackson
2019-11-19 12:40 ` Oleksandr Grytsov
2019-11-20 16:04 ` Ian Jackson
2019-10-08 14:10 ` [Xen-devel] [PATCH v1 2/2] libxl: add removing XS backend path for PV devices on domain destroy Oleksandr Grytsov
2019-10-11 15:07 ` Ian Jackson
2019-10-11 15:32 ` Roger Pau Monné
2019-10-11 15:55 ` Ian Jackson
2019-10-15 15:39 ` Roger Pau Monné
2019-10-16 10:39 ` 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=23968.39034.34800.276030@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=al1img@gmail.com \
--cc=oleksandr_grytsov@epam.com \
--cc=wl@xen.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;
as well as URLs for NNTP newsgroup(s).