From: Anthony Liguori <anthony@codemonkey.ws>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, cfergeau@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4] ps2: migrate ledstate
Date: Mon, 17 Oct 2011 08:37:17 -0500 [thread overview]
Message-ID: <4E9C2F8D.4050105@codemonkey.ws> (raw)
In-Reply-To: <1318851454-22335-1-git-send-email-quintela@redhat.com>
On 10/17/2011 06:37 AM, Juan Quintela wrote:
> From: Christophe Fergeau<cfergeau@redhat.com>
>
> Make the ps2 device track its ledstate so that we can migrate it.
> Otherwise it gets lost across migration, and spice-server gets
> confused about the actual keyboard state and sends bogus
> caps/scroll/num key events. This fixes RH bug #729294
>
> We only need to migrate the state when it is different of the default
> one (0).
Er, isn't it going to be different from the default in like 99% of circumstances?
I think in cases where you're usually going to send a subsection, bumping the
version is better.
Regards,
Anthony Liguori
>
> Signed-off-by: Christophe Fergeau<cfergeau@redhat.com>
> Signed-off-by: Juan Quintela<quintela@redhat.com>
> ---
> hw/ps2.c | 46 ++++++++++++++++++++++++++++++++++++++++++++--
> 1 files changed, 44 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ps2.c b/hw/ps2.c
> index 24228c1..1d9057b 100644
> --- a/hw/ps2.c
> +++ b/hw/ps2.c
> @@ -92,6 +92,7 @@ typedef struct {
> not the keyboard controller. */
> int translate;
> int scancode_set; /* 1=XT, 2=AT, 3=PS/2 */
> + int ledstate;
> } PS2KbdState;
>
> typedef struct {
> @@ -195,11 +196,17 @@ uint32_t ps2_read_data(void *opaque)
> return val;
> }
>
> +static void ps2_set_ledstate(PS2KbdState *s, int ledstate)
> +{
> + s->ledstate = ledstate;
> + kbd_put_ledstate(ledstate);
> +}
> +
> static void ps2_reset_keyboard(PS2KbdState *s)
> {
> s->scan_enabled = 1;
> s->scancode_set = 2;
> - kbd_put_ledstate(0);
> + ps2_set_ledstate(s, 0);
> }
>
> void ps2_write_keyboard(void *opaque, int val)
> @@ -274,7 +281,7 @@ void ps2_write_keyboard(void *opaque, int val)
> s->common.write_cmd = -1;
> break;
> case KBD_CMD_SET_LEDS:
> - kbd_put_ledstate(val);
> + ps2_set_ledstate(s, val);
> ps2_queue(&s->common, KBD_REPLY_ACK);
> s->common.write_cmd = -1;
> break;
> @@ -557,6 +564,33 @@ static const VMStateDescription vmstate_ps2_common = {
> }
> };
>
> +static bool ps2_keyboard_ledstate_needed(void *opaque)
> +{
> + PS2KbdState *s = opaque;
> +
> + return s->ledstate != 0; /* 0 is default state */
> +}
> +
> +static int ps2_kbd_ledstate_post_load(void *opaque, int version_id)
> +{
> + PS2KbdState *s = opaque;
> +
> + kbd_put_ledstate(s->ledstate);
> + return 0;
> +}
> +
> +static const VMStateDescription vmstate_ps2_keyboard_ledstate = {
> + .name = "ps2kbd/ledstate",
> + .version_id = 3,
> + .minimum_version_id = 2,
> + .minimum_version_id_old = 2,
> + .post_load = ps2_kbd_ledstate_post_load,
> + .fields = (VMStateField []) {
> + VMSTATE_INT32(ledstate, PS2KbdState),
> + VMSTATE_END_OF_LIST()
> + }
> +};
> +
> static int ps2_kbd_post_load(void* opaque, int version_id)
> {
> PS2KbdState *s = (PS2KbdState*)opaque;
> @@ -578,6 +612,14 @@ static const VMStateDescription vmstate_ps2_keyboard = {
> VMSTATE_INT32(translate, PS2KbdState),
> VMSTATE_INT32_V(scancode_set, PS2KbdState,3),
> VMSTATE_END_OF_LIST()
> + },
> + .subsections = (VMStateSubsection []) {
> + {
> + .vmsd =&vmstate_ps2_keyboard_ledstate,
> + .needed = ps2_keyboard_ledstate_needed,
> + }, {
> + /* empty */
> + }
> }
> };
>
next prev parent reply other threads:[~2011-10-17 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 11:37 [Qemu-devel] [PATCH v4] ps2: migrate ledstate Juan Quintela
2011-10-17 13:35 ` Christophe Fergeau
2011-10-17 13:37 ` Anthony Liguori [this message]
2011-10-17 15:15 ` Gerd Hoffmann
2011-10-17 15:21 ` Juan Quintela
2011-10-17 15:24 ` Anthony Liguori
2011-11-01 22:21 ` 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=4E9C2F8D.4050105@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=cfergeau@redhat.com \
--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.