From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: ChenLiang <chenliang88@huawei.com>, Gonglei <arei.gonglei@huawei.com>
Subject: [Qemu-devel] [PULL 01/11] pit: fix pit interrupt can't inject into vm after migration
Date: Fri, 26 Sep 2014 16:38:00 +0200 [thread overview]
Message-ID: <1411742290-2940-2-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1411742290-2940-1-git-send-email-pbonzini@redhat.com>
From: ChenLiang <chenliang88@huawei.com>
kvm_pit is running in kmod. kvm_pit is going to inject
interrupt to vm before cpu_synchronize_all_post_init at
dest side. vcpu will lose the pit interrupt, but
ack_irq(in kmod) has been 0. ack_irq become 1 after
vcpu responds pit interrupt. pit interruptcan inject
to vm when ack_irq is 1.
By the way, kvm_pit_vm_state_change has save and load
state of pit, so pre_save and post_load is unnecessary.
Signed-off-by: ChenLiang <chenliang88@huawei.com>
Signed-off-by: Gonglei <arei.gonglei@huawei.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
hw/i386/kvm/i8254.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/hw/i386/kvm/i8254.c b/hw/i386/kvm/i8254.c
index 59373aa..472af81 100644
--- a/hw/i386/kvm/i8254.c
+++ b/hw/i386/kvm/i8254.c
@@ -239,6 +239,7 @@ static void kvm_pit_vm_state_change(void *opaque, int running,
if (running) {
kvm_pit_update_clock_offset(s);
+ kvm_pit_put(PIT_COMMON(s));
s->vm_stopped = false;
} else {
kvm_pit_update_clock_offset(s);
@@ -314,8 +315,6 @@ static void kvm_pit_class_init(ObjectClass *klass, void *data)
dc->realize = kvm_pit_realizefn;
k->set_channel_gate = kvm_pit_set_gate;
k->get_channel_info = kvm_pit_get_channel_info;
- k->pre_save = kvm_pit_get;
- k->post_load = kvm_pit_put;
dc->reset = kvm_pit_reset;
dc->props = kvm_pit_properties;
}
--
2.1.0
next prev parent reply other threads:[~2014-09-26 14:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 14:37 [Qemu-devel] [PULL 00/11] KVM (and more) patches for 2014-09-26 Paolo Bonzini
2014-09-26 14:38 ` Paolo Bonzini [this message]
2014-09-26 14:38 ` [Qemu-devel] [PULL 02/11] Introduce cpu_clean_all_dirty Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 03/11] kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 04/11] kvmclock: Ensure time in migration never goes backward Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 05/11] hw/dma/i8257: Silence phony error message Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 06/11] target-i386: update fp status fix Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 07/11] serial: reset state at startup Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 08/11] serial: check if backed by a physical serial port at realize time Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 09/11] kvmvapic: fix migration when VM paused and when not running Windows Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 10/11] po: fix conflict with %.mo rule in rules.mak Paolo Bonzini
2014-09-26 14:38 ` [Qemu-devel] [PULL 11/11] kvm/valgrind: don't mark memory as initialized Paolo Bonzini
2014-09-26 17:16 ` [Qemu-devel] [PULL 00/11] KVM (and more) patches for 2014-09-26 Peter Maydell
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=1411742290-2940-2-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=chenliang88@huawei.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).