From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "avi@redhat.com" <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] call kvm_cpu_synchronize_state() on target vcpu
Date: Wed, 09 Sep 2009 18:21:48 +0200 [thread overview]
Message-ID: <4AA7D61C.7080004@siemens.com> (raw)
In-Reply-To: <20090909160734.GG22885@redhat.com>
Gleb Natapov wrote:
> On Wed, Sep 09, 2009 at 05:57:40PM +0200, Jan Kiszka wrote:
>> Gleb Natapov wrote:
>>> On Wed, Sep 09, 2009 at 05:47:13PM +0200, Jan Kiszka wrote:
>>>> Gleb Natapov wrote:
>>>>> regs_modified logic doesn't work if io thread calls
>>>>> kvm_cpu_synchronize_state() since kvm_arch_get_registers()
>>>>> returns only after vcpu thread is back to kernel. Setting
>>>>> regs_modified to 1 at this stage causes loading of wrong vcpu
>>>>> state on the next vcpu_run().
>>>> We need this upstream too, right? Could you file the corresponding patch?
>>>>
>>> Upstream is single threaded. It shouldn't suffer from this bug.
>> Not if you enable iothread support (though I don't remember if that
> It can't work with kvm since all vcpu ioctls are called on the thread
> that issues them.
Yeah, I just recalled all that on_vcpu fuzz and that upstream is still
horribly broken /wrt iothread+kvm. But once that is fixed, we also need
this fix here.
>
>> works now for kvm) + you are also touching shared code here. So qemu-kvm
>> would benefit from keeping the diff small.
>>
> The patch doesn't touch shared code. (it is almost impossible to tell
> what code is shared and what's not nowadays)
cpu_dump_state() is definitely shared.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-09-09 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:33 [PATCH] call kvm_cpu_synchronize_state() on target vcpu Gleb Natapov
2009-09-09 15:41 ` Avi Kivity
2009-09-09 15:47 ` Jan Kiszka
2009-09-09 15:49 ` Gleb Natapov
2009-09-09 15:57 ` Jan Kiszka
2009-09-09 16:07 ` Gleb Natapov
2009-09-09 16:21 ` Jan Kiszka [this message]
2009-09-09 16:27 ` Gleb Natapov
2009-09-09 16:32 ` Jan Kiszka
2009-09-09 16:36 ` 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=4AA7D61C.7080004@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.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;
as well as URLs for NNTP newsgroup(s).