From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, Jan Kiszka <jan.kiszka@web.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] i386/vmmouse: Properly reset state
Date: Thu, 29 Aug 2019 20:00:37 +0200 [thread overview]
Message-ID: <055f099e-c9a7-1d75-7dcc-0d8916988cc6@redhat.com> (raw)
In-Reply-To: <20190827194948.GB7077@habkost.net>
Hi Jan,
On 8/27/19 9:49 PM, Eduardo Habkost wrote:
> On Sun, Aug 25, 2019 at 04:58:18PM +0200, Jan Kiszka wrote:
>> On 21.07.19 10:58, Jan Kiszka wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> nb_queue was not zeroed so that we no longer delivered events if a
>>> previous guest left the device in an overflow state.
>>>
>>> The state of absolute does not matter as the next vmmouse_update_handler
>>> call will align it again.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> ---
>>> hw/i386/vmmouse.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/hw/i386/vmmouse.c b/hw/i386/vmmouse.c
>>> index 5d2d278be4..e335bd07da 100644
>>> --- a/hw/i386/vmmouse.c
>>> +++ b/hw/i386/vmmouse.c
>>> @@ -257,6 +257,7 @@ static void vmmouse_reset(DeviceState *d)
>>> VMMouseState *s = VMMOUSE(d);
>>>
>>> s->queue_size = VMMOUSE_QUEUE_SIZE;
>>> + s->nb_queue = 0;
Don't we also need to reset the status in case vmmouse_get_status() is
called directly after reset?
s->status = 0;
With it:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>
>>> vmmouse_disable(s);
>>> }
>>> --
>>> 2.16.4
>>>
>>>
>>
>> Ping - or who is looking after this?
>
> Despite being in hw/i386, I think we can say vmmouse.c doesn't
> have a maintainer. Last time someone changed vmmouse.c in a
> meaningful way (not just adapting to API changes or removing
> duplicate code) was in 2012.
>
Well it does has a few:
$ ./scripts/get_maintainer.pl -f hw/i386/vmmouse.c
"Michael S. Tsirkin" <mst@redhat.com> (supporter:PC)
Marcel Apfelbaum <marcel.apfelbaum@gmail.com> (supporter:PC)
Paolo Bonzini <pbonzini@redhat.com> (maintainer:X86 TCG CPUs)
Richard Henderson <rth@twiddle.net> (maintainer:X86 TCG CPUs)
Eduardo Habkost <ehabkost@redhat.com> (maintainer:X86 TCG CPUs)
However the correct section should rather be "PC Chipset".
> But the change makes sense to me, so:
>
> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
>
> I'll queue it.
>
next prev parent reply other threads:[~2019-08-29 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 8:58 [Qemu-devel] [PATCH] i386/vmmouse: Properly reset state Jan Kiszka
2019-08-25 14:58 ` Jan Kiszka
2019-08-27 19:49 ` Eduardo Habkost
2019-08-29 18:00 ` Philippe Mathieu-Daudé [this message]
2019-08-29 18:12 ` Jan Kiszka
2019-08-29 18:38 ` Philippe Mathieu-Daudé
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=055f099e-c9a7-1d75-7dcc-0d8916988cc6@redhat.com \
--to=philmd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jan.kiszka@web.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).