From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Gao Zhiyuan" <zgao@suse.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Can I have someone's feedback on [bug 1809075] Concurrency bug on keyboard events: capslock LED messing up keycode streams causes character misses at guest kernel
Date: Thu, 3 Jan 2019 12:05:54 +0100 [thread overview]
Message-ID: <e51bd6dc-e135-b66a-189d-8b79bc5f7e49@redhat.com> (raw)
In-Reply-To: <ddc7219f-98c3-28be-084f-64606452e49b@suse.com>
Cc'ing Marc-André & Gerd.
On 12/19/18 10:31 AM, Gao Zhiyuan wrote:
> Hi everyone.
>
> Can I please have someone's feedback on this bug?
> https://bugs.launchpad.net/qemu/+bug/1809075
> Briefly, guest OS loses characters sent to it via vnc. And I spot the
> bug in relation to ps2 driver.
>
> I'm thinking of possible fixes and I might want to use a memory barrier.
> But I would really like to have some suggestion from a qemu developer
> first. For example, can we brutally drop capslock LED key events in ps2
> queue?
>
> It is actually relevant to openQA, an automated QA tool for openSUSE.
> And this bug blocks a few test cases for us.
>
> Thank you in advance!
>
> Kind regards,
> Gao Zhiyuan
>
next prev parent reply other threads:[~2019-01-03 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 9:31 [Qemu-devel] Can I have someone's feedback on [bug 1809075] Concurrency bug on keyboard events: capslock LED messing up keycode streams causes character misses at guest kernel Gao Zhiyuan
2019-01-03 11:05 ` Philippe Mathieu-Daudé [this message]
2019-01-07 8:16 ` Gerd Hoffmann
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=e51bd6dc-e135-b66a-189d-8b79bc5f7e49@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zgao@suse.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).