From: Gleb Natapov <gleb@redhat.com>
To: Beth Kon <eak@us.ibm.com>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 4/5] Userspace changes for qemu-kvm HPET support(v8)
Date: Tue, 7 Jul 2009 14:57:28 +0300 [thread overview]
Message-ID: <20090707115728.GD28046@redhat.com> (raw)
In-Reply-To: <1246420759-12502-4-git-send-email-eak@us.ibm.com>
On Tue, Jun 30, 2009 at 11:59:18PM -0400, Beth Kon wrote:
> @@ -89,8 +95,12 @@ static int kvm_pit_load(QEMUFile *f, void *opaque, int version_id)
> c->count_load_time = sc->count_load_time;
> }
>
> - kvm_set_pit(kvm_context, &pit);
> -
> + if(qemu_kvm_has_pit_state2()) {
> + kvm_set_pit2(kvm_context, &pit2);
> + return 0;
Return is not needed here.
> + } else {
> + kvm_set_pit(kvm_context, (struct kvm_pit_state *)&pit2);
> + }
> return 0;
> }
>
[skip]
> @@ -390,6 +397,7 @@ void pit_save(QEMUFile *f, void *opaque)
> PITChannelState *s;
> int i;
>
> + qemu_put_be32(f, pit->flags);
> for(i = 0; i < 3; i++) {
> s = &pit->channels[i];
> qemu_put_be32(f, s->count);
> @@ -421,6 +429,7 @@ int pit_load(QEMUFile *f, void *opaque, int version_id)
> if (version_id != 1)
> return -EINVAL;
>
> + pit->flags = qemu_get_be32(f);
> for(i = 0; i < 3; i++) {
> s = &pit->channels[i];
> s->count=qemu_get_be32(f);
If migration data format changes you need to advance savevm version_id.
--
Gleb.
next prev parent reply other threads:[~2009-07-07 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 3:59 [PATCH 1/5] BIOS changes for irq0->inti2 override (v8) Beth Kon
2009-07-01 3:59 ` [PATCH 2/5] Userspace changes for irq0->inti2 override support (v8) Beth Kon
2009-07-01 3:59 ` [PATCH 3/5] BIOS changes for qemu-kvm hpet " Beth Kon
2009-07-01 3:59 ` [PATCH 4/5] Userspace changes for qemu-kvm HPET support(v8) Beth Kon
2009-07-07 11:57 ` Gleb Natapov [this message]
2009-07-01 3:59 ` [PATCH 5/5] Kernel changes for HPET legacy support(v8) Beth Kon
2009-07-07 11:58 ` [PATCH 1/5] BIOS changes for irq0->inti2 override (v8) Gleb Natapov
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=20090707115728.GD28046@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=eak@us.ibm.com \
--cc=kvm@vger.kernel.org \
/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