From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [RFC][PATCH] qemu-kvm: Introduce writeback scope for cpu_synchronize_state
Date: Wed, 18 Nov 2009 15:48:35 +0200 [thread overview]
Message-ID: <4B03FB33.3070408@redhat.com> (raw)
In-Reply-To: <4B02D635.6070805@web.de>
On 11/17/2009 06:58 PM, Jan Kiszka wrote:
>
>> That wouldn't be required anymore with the "always queue" policy.
>>
> Hmm, unless we need mp_state manipulation analogously to KVM_NMI vs.
> KVM_SET_VCPU_STATE: The former will queue, the latter write, but may be
> overwritten by anything queued. If you just queue KVM_SET_MP_STATE, you
> still have a conflict between concurrent manipulations from user space,
> something we want to resolve automagically.
>
The idea is to queue. But queueing INIT state clears the queue (we're
pretending to send an INIT signal over the apic bus).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-11-18 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 17:00 [RFC][PATCH] qemu-kvm: Introduce writeback scope for cpu_synchronize_state Jan Kiszka
2009-11-16 18:20 ` Alexander Graf
2009-11-16 19:14 ` Avi Kivity
2009-11-16 21:22 ` Jan Kiszka
2009-11-17 8:05 ` Avi Kivity
2009-11-17 8:14 ` Jan Kiszka
2009-11-17 8:37 ` Avi Kivity
2009-11-17 9:16 ` Jan Kiszka
2009-11-17 12:37 ` Avi Kivity
2009-11-17 13:05 ` Jan Kiszka
2009-11-17 13:28 ` Avi Kivity
2009-11-17 14:12 ` Jan Kiszka
2009-11-17 14:25 ` Avi Kivity
2009-11-17 16:50 ` Jan Kiszka
2009-11-17 16:58 ` Jan Kiszka
2009-11-18 13:48 ` Avi Kivity [this message]
2009-11-17 16:59 ` Avi Kivity
2009-11-18 9:50 ` Jan Kiszka
2009-11-18 13:46 ` Avi Kivity
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=4B03FB33.3070408@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox