From: Gleb Natapov <gleb@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel@nongnu.org, Glauber Costa <glommer@redhat.com>,
Avi Kivity <avi@redhat.com>,
aliguori@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH 5/7] tell kernel about all registers instead of just mp_state
Date: Mon, 30 Nov 2009 14:04:44 +0200 [thread overview]
Message-ID: <20091130120444.GH30150@redhat.com> (raw)
In-Reply-To: <5d6222a80911300345w3df34c9bvad12344df484d935@mail.gmail.com>
On Mon, Nov 30, 2009 at 09:45:56AM -0200, Glauber Costa wrote:
> >> since
> >> + * apic base was just updated
> >> + */
> >> + kvm_arch_put_registers(s->cpu_env);
> >>
> >>
> >
> > Better to use cpu_synchronize_state() instead.
> >
> I might be misreading it, but :
>
> void kvm_cpu_synchronize_state(CPUState *env)
> {
> if (!env->kvm_state->regs_modified) {
> kvm_arch_get_registers(env);
> env->kvm_state->regs_modified = 1;
> }
> }
>
> Only does get. And we need put.
>
Put is on the entry into the kernel in vcpu_run.
--
Gleb.
next prev parent reply other threads:[~2009-11-30 12:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 17:24 [Qemu-devel] [PATCH 0/7] KVM SMP support, early version Glauber Costa
2009-11-26 17:24 ` [Qemu-devel] [PATCH 1/7] Don't mess with halted state Glauber Costa
2009-11-26 17:24 ` [Qemu-devel] [PATCH 2/7] store thread-specific env information Glauber Costa
2009-11-26 17:24 ` [Qemu-devel] [PATCH 3/7] update halted state on mp_state sync Glauber Costa
2009-11-26 17:24 ` [Qemu-devel] [PATCH 4/7] qemu_flush_work for remote vcpu execution Glauber Costa
2009-11-26 17:24 ` [Qemu-devel] [PATCH 5/7] tell kernel about all registers instead of just mp_state Glauber Costa
2009-11-26 17:24 ` [Qemu-devel] [PATCH 6/7] Don't call kvm cpu reset on initialization Glauber Costa
2009-11-26 17:25 ` [Qemu-devel] [PATCH 7/7] remove smp restriction from kvm Glauber Costa
2009-11-29 15:32 ` [Qemu-devel] [PATCH 5/7] tell kernel about all registers instead of just mp_state Avi Kivity
2009-11-30 11:45 ` Glauber Costa
2009-11-30 12:04 ` Gleb Natapov [this message]
2009-11-30 12:05 ` Avi Kivity
2009-11-30 13:31 ` Glauber Costa
2009-11-30 13:32 ` Avi Kivity
2009-11-29 15:32 ` [Qemu-devel] [PATCH 4/7] qemu_flush_work for remote vcpu execution Avi Kivity
2009-11-30 11:44 ` Glauber Costa
2009-11-30 12:06 ` Avi Kivity
2009-11-30 11:48 ` [Qemu-devel] " Paolo Bonzini
2009-11-29 15:29 ` [Qemu-devel] [PATCH 2/7] store thread-specific env information Avi Kivity
2009-11-29 15:38 ` Andreas Färber
2009-11-29 15:42 ` Avi Kivity
2009-11-29 16:00 ` Andreas Färber
2009-11-29 22:29 ` Jamie Lokier
2009-11-30 11:36 ` [Qemu-devel] " Paolo Bonzini
2009-11-30 11:41 ` Glauber Costa
2009-11-30 11:49 ` Paolo Bonzini
2009-11-30 12:07 ` Avi Kivity
2009-11-29 17:32 ` [Qemu-devel] Re: [PATCH 0/7] KVM SMP support, early version Jan Kiszka
2009-11-30 11:42 ` Glauber Costa
2009-11-30 15:55 ` Glauber Costa
2009-11-30 16:40 ` Avi Kivity
2009-11-30 16:47 ` Glauber Costa
2009-11-30 17:30 ` Jan Kiszka
2009-12-01 12:10 ` Avi Kivity
2009-12-01 12:17 ` Jan Kiszka
2009-12-01 12:20 ` Glauber Costa
2009-12-01 12:33 ` Jan Kiszka
2009-11-30 16:50 ` Avi Kivity
2009-12-01 0:31 ` [Qemu-devel] " Ed Swierk
2009-12-01 0:42 ` Ed Swierk
2009-12-01 12:20 ` Alexander Graf
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=20091130120444.GH30150@redhat.com \
--to=gleb@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@gmail.com \
--cc=glommer@redhat.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).