From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: xen-devel@lists.xenproject.org, dmitry.torokhov@gmail.com,
jandryuk@gmail.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v3] xen/kbdif: Add features to disable keyboard and pointer
Date: Wed, 2 May 2018 09:58:00 -0400 [thread overview]
Message-ID: <20180502135800.GA8727@char.us.oracle.com> (raw)
In-Reply-To: <20180502071608.26864-1-andr2000@gmail.com>
On Wed, May 02, 2018 at 10:16:08AM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> It is now not fully possible to control if and which virtual devices
> are created by the frontend, e.g. keyboard and pointer devices
> are always created and multi-touch device is created if the
> backend advertises multi-touch support. In some cases this
> behavior is not desirable and better control over the frontend's
> configuration is required.
>
> Add new XenStore feature fields, so it is possible to individually
> control set of exposed virtual devices for each guest OS:
> - set feature-disable-keyboard to 1 if no keyboard device needs
> to be created
> - set feature-disable-pointer to 1 if no pointer device needs
> to be created
>
> Keep old behavior by default.
>
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Thank you!
> ---
> xen/include/public/io/kbdif.h | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/xen/include/public/io/kbdif.h b/xen/include/public/io/kbdif.h
> index 3ce54e9a44c1..9a0648bdced9 100644
> --- a/xen/include/public/io/kbdif.h
> +++ b/xen/include/public/io/kbdif.h
> @@ -51,6 +51,18 @@
> * corresponding entries in XenStore and puts 1 as the value of the entry.
> * If a feature is not supported then 0 must be set or feature entry omitted.
> *
> + * feature-disable-keyboard
> + * Values: <uint>
> + *
> + * If there is no need to expose a virtual keyboard device by the
> + * frontend then this must be set to 1.
> + *
> + * feature-disable-pointer
> + * Values: <uint>
> + *
> + * If there is no need to expose a virtual pointer device by the
> + * frontend then this must be set to 1.
> + *
> * feature-abs-pointer
> * Values: <uint>
> *
> @@ -177,6 +189,8 @@
>
> #define XENKBD_DRIVER_NAME "vkbd"
>
> +#define XENKBD_FIELD_FEAT_DSBL_KEYBRD "feature-disable-keyboard"
> +#define XENKBD_FIELD_FEAT_DSBL_POINTER "feature-disable-pointer"
> #define XENKBD_FIELD_FEAT_ABS_POINTER "feature-abs-pointer"
> #define XENKBD_FIELD_FEAT_MTOUCH "feature-multi-touch"
> #define XENKBD_FIELD_REQ_ABS_POINTER "request-abs-pointer"
> --
> 2.17.0
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-02 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 7:16 [PATCH v3] xen/kbdif: Add features to disable keyboard and pointer Oleksandr Andrushchenko
2018-05-02 13:58 ` Konrad Rzeszutek Wilk [this message]
2018-05-02 14:18 ` Oleksandr Andrushchenko
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=20180502135800.GA8727@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andr2000@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jandryuk@gmail.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).