From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
Dinar Valeev <dvaleev@suse.de>, Dirk Mueller <dmueller@suse.com>
Subject: Re: [Qemu-devel] [PATCH] hid: Extend the event queue size to 1024
Date: Mon, 18 Apr 2016 11:21:38 +0200 [thread overview]
Message-ID: <1460971298.21910.13.camel@redhat.com> (raw)
In-Reply-To: <57148C37.90807@suse.de>
On Mo, 2016-04-18 at 09:26 +0200, Alexander Graf wrote:
>
> On 18.04.16 08:53, Gerd Hoffmann wrote:
> > Hi,
> >
> >> Vnc already uses qemu_input_event_send_key_delay today, so I'm not sure
> >> where things fall apart.
> >
> > Well, not everywhere. Try the attached patch.
> >
> > Also worth trying:
> > * use xhci instead of ohci (current slof should handle
> > kbd-via-xhci fine)
> > * use virtio-keyboard (no slof driver yet as far I know, also needs
> > a recent linux kernel).
>
> Ideally I would really like to switch to virtio-input and virtio-gpu for
> AArch64, but there are no drivers at all in OVMF. Do you have any plans
> to write them?
Not investigated yet. There are virtio 1.0 patches in flight for edk2,
once they are landed it should be alot simpler (virtio 1.0 is mandatory
for virtio-gpu and virtio-input).
Keyboard should be easy, it's a simple device.
GPU is tricky. Guest is expected to explicitly request display updates.
So simply setting up a dump framebuffer, then depending on dirty page
tracking for screen updates isn't going to fly. Not sure EFI can handle
that.
The virtio-vga device has a vga compatibility mode additionally to
native virtio. SLOF uses that IIRC. But I think on aarch64 that isn't
going to fly either due to the cache coherency issues there.
cheers,
Gerd
next prev parent reply other threads:[~2016-04-18 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 14:25 [Qemu-devel] [PATCH] hid: Extend the event queue size to 1024 Alexander Graf
2016-04-14 15:17 ` Gerd Hoffmann
2016-04-14 15:29 ` Alexander Graf
2016-04-14 16:19 ` Gerd Hoffmann
2016-04-15 12:18 ` Dinar Valeev
2016-04-18 6:53 ` Gerd Hoffmann
2016-04-18 7:26 ` Alexander Graf
2016-04-18 9:21 ` Gerd Hoffmann [this message]
2016-04-18 9:27 ` Alexander Graf
2016-04-19 9:28 ` Juan Quintela
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=1460971298.21910.13.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=dmueller@suse.com \
--cc=dvaleev@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).