From: Luiz Capitulino <lcapitulino@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: peter.maydell@linaro.org, Anthony Liguori <aliguori@us.ibm.com>,
lilei@linux.vnet.ibm.com, quintela@redhat.com,
qemu-devel@nongnu.org, armbru@redhat.com, kraxel@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>,
lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/2] ps2: add support of auto-repeat
Date: Mon, 17 Jun 2013 09:01:58 -0400 [thread overview]
Message-ID: <20130617090158.66667be9@redhat.com> (raw)
In-Reply-To: <20130614054641.GA30532@t430s.nay.redhat.com>
On Fri, 14 Jun 2013 13:46:41 +0800
Amos Kong <akong@redhat.com> wrote:
> On Fri, May 31, 2013 at 08:31:17PM +0800, Amos Kong wrote:
> > On Thu, May 30, 2013 at 11:48:46AM -0500, Anthony Liguori wrote:
> > > Amos Kong <akong@redhat.com> writes:
>
>
> > > > diff --git a/hw/input/ps2.c b/hw/input/ps2.c
> > > > index 3412079..8adbb4a 100644
> > > > --- a/hw/input/ps2.c
> > > > +++ b/hw/input/ps2.c
> > > > @@ -94,6 +94,10 @@ typedef struct {
> > > > int translate;
> > > > int scancode_set; /* 1=XT, 2=AT, 3=PS/2 */
> > > > int ledstate;
> > > > + int repeat_period; /* typematic period, ms */
> > > > + int repeat_delay; /* typematic delay, ms */
> > > > + int repeat_key; /* keycode to repeat */
> > > > + QEMUTimer *repeat_timer;
> > >
> > > This state needs to be migrated, no? I suspect it can/should be done
> > > via a subsection too.
> >
> > It sounds only reasonable for 'sendkey' command. We want to repeat one
> > key for 100 times, the key should be continaully repeated in the dest
> > vm until it reaches to 100 times.
> >
> > For implement this, we should also migrate key_timer in ui/input.c,
> > then it will send a release event to ps2 queue when the key_timer
> > is expired. The bottom patch migrates repeat_timer & repeat_key,
> > where should we save key_timer for migration?
>
> Luiz, any suggestion about migrate the key_timer in ui/input.c?
I don't have any. Maybe Markus or Juan can help (CC'ed).
>
> We need to migrate it, then sendkey can continually work in dest vm
> until the timer is expired.
>
> Thanks.
next prev parent reply other threads:[~2013-06-17 13:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 16:10 [Qemu-devel] [PATCH v2 0/2] ps2 auto-repeat Amos Kong
2013-05-22 16:10 ` [Qemu-devel] [PATCH v2 1/2] ps2: add support of auto-repeat Amos Kong
2013-05-30 16:48 ` Anthony Liguori
2013-05-31 12:31 ` Amos Kong
2013-06-13 10:04 ` Amos Kong
2013-06-13 12:01 ` Anthony Liguori
2013-06-13 10:19 ` Andreas Färber
2013-06-13 12:34 ` Paolo Bonzini
2013-06-13 13:01 ` Anthony Liguori
2013-06-13 14:47 ` Paolo Bonzini
2013-06-13 18:28 ` Anthony Liguori
2013-06-14 3:45 ` Amos Kong
2013-06-14 5:46 ` Amos Kong
2013-06-17 13:01 ` Luiz Capitulino [this message]
2013-06-26 11:56 ` Markus Armbruster
2013-07-02 6:49 ` Amos Kong
2013-07-23 12:43 ` Gerd Hoffmann
2013-05-22 16:10 ` [Qemu-devel] [PATCH v2 2/2] ps2: preserve repeat state on migration Amos Kong
2013-05-30 16:49 ` Anthony Liguori
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=20130617090158.66667be9@redhat.com \
--to=lcapitulino@redhat.com \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=lilei@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.