From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Owen Smith <owen.smith@citrix.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org
Subject: Re: [PATCH] kbdif: Define "feature-raw-pointer" and "request-raw-pointer"
Date: Tue, 4 Jul 2017 08:52:21 +0300 [thread overview]
Message-ID: <81ca71d8-b192-e52a-c4ad-4e11328e563f@gmail.com> (raw)
In-Reply-To: <1499086673-1877-1-git-send-email-owen.smith@citrix.com>
Hi, Owen!
On 07/03/2017 03:57 PM, Owen Smith wrote:
> determine the difference between older
> backends and newer backends. In the case I'm interested in, the difference
> between old QEMU vkbd backend which blocks waiting for the vfb device, which
> is not present on HVM guests, and a newer QEMU backend
For how long will it remain "new" and what will be the
next patch for yet another new backend?
So, in addition to your patch I would suggest we add backend
type and its version to get the information you need and rely
on that deterministically, not making indirect decisions on
if the pointer is raw for new backend only.
Please see [1] where backend "type" entry was discussed.
BTW, we are working on decoupling QEMU's vkbd from vfb
as it is required for vkbd to work with vdispl, not vfb,
so from having type and version we will also benefit.
Thank you,
Oleksandr
[1] https://patchwork.kernel.org/patch/9674807/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-04 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 12:57 [PATCH] kbdif: Define "feature-raw-pointer" and "request-raw-pointer" Owen Smith
2017-07-03 14:19 ` Paul Durrant
2017-07-03 23:49 ` Stefano Stabellini
2017-07-18 22:29 ` Stefano Stabellini
2017-07-19 1:41 ` Konrad Rzeszutek Wilk
2017-07-04 5:52 ` Oleksandr Andrushchenko [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=81ca71d8-b192-e52a-c4ad-4e11328e563f@gmail.com \
--to=andr2000@gmail.com \
--cc=owen.smith@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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).