From: Gerd Hoffmann <kraxel@redhat.com>
To: Ladi Prosek <lprosek@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-input: implement pass-through evdev writes
Date: Fri, 01 Apr 2016 12:20:23 +0200 [thread overview]
Message-ID: <1459506023.7011.55.camel@redhat.com> (raw)
In-Reply-To: <1459503073-9684-1-git-send-email-lprosek@redhat.com>
On Fr, 2016-04-01 at 11:31 +0200, Ladi Prosek wrote:
> The write path for pass-through devices, commonly used for controlling
> keyboard LEDs via EV_LED, was not implemented. This commit adds the
> necessary plumbing to connect the status virtio queue to the host evdev
> file descriptor.
>
> Signed-off-by: Ladi Prosek <lprosek@redhat.com>
> ---
> Most of the new code has to do with handling EAGAIN/EWOULDBLOCK. I don't
> believe that this will be happening in practise for local evdev devices.
Agree.
> Of course, all bets are off if fd is an arbitrary file,
It can't be, it would fail the evdev ioctls.
> with the event stream). So part of me would just do one best-effort
> write and ignore all errors. I'm curious what you think.
Just do best-effort sounds reasonable to me.
The code to handle EGAIN will just bitrot b/c it will never be used (and
I guess it is untested too, or did you manage to provoke EGAIN somehow?)
cheers,
Gerd
next prev parent reply other threads:[~2016-04-01 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 9:31 [Qemu-devel] [PATCH] virtio-input: implement pass-through evdev writes Ladi Prosek
2016-04-01 10:20 ` Gerd Hoffmann [this message]
2016-04-01 10:24 ` Ladi Prosek
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=1459506023.7011.55.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=lprosek@redhat.com \
--cc=qemu-devel@nongnu.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).