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:46:50 +0200 [thread overview]
Message-ID: <4B03FACA.3010500@redhat.com> (raw)
In-Reply-To: <4B03C348.4010604@web.de>
On 11/18/2009 11:50 AM, Jan Kiszka wrote:
>
>> INIT, too.
>>
> INIT should be handled by queuing up the next mp_state.
>
And clearing the previous queue; otherwise our queue is unbounded.
> BTW, as we do not inject mp_state changes from user space during
> runtime, the issue I saw with the current interface is not existing. We
> just need to add that queuing feature to asynchronous in-kernel mp_state
> changes, and we should be fine.
>
>
> Let's assume we will have such changes in future kernels: should
> qemu-kvm and qemu upstream also bother about older kernels and establish
> workarounds? Because then we need to find a cleaner approach than the
> current one, and my proposed patch comes into the game again.
>
If we treat this as a bug, then we fix the older kernels too.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-11-18 13:46 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
2009-11-17 16:59 ` Avi Kivity
2009-11-18 9:50 ` Jan Kiszka
2009-11-18 13:46 ` Avi Kivity [this message]
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=4B03FACA.3010500@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.