From: Avi Kivity <avi@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] qemu-kvm: introduce cpu_start/cpu_stop commands
Date: Tue, 23 Nov 2010 08:35:03 +0200 [thread overview]
Message-ID: <4CEB6097.2030203@redhat.com> (raw)
In-Reply-To: <20101122230405.GB10050@sequoia.sous-sol.org>
On 11/23/2010 01:04 AM, Chris Wright wrote:
> * Anthony Liguori (aliguori@us.ibm.com) wrote:
> > qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching
> > them to respond to these signals, introduce monitor commands that stop and start
> > individual vcpus.
>
> In the past SIGSTOP has introduced time skew. Have you verified this
> isn't an issue.
Wouldn't we have the same problems with kernel cpu limits? I'd say it
only depends on the period of the controller, not on how it's implemented.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-11-23 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 23:00 [PATCH] qemu-kvm: introduce cpu_start/cpu_stop commands Anthony Liguori
2010-11-22 23:03 ` Anthony Liguori
2010-11-22 23:04 ` Chris Wright
2010-11-22 23:44 ` Anthony Liguori
2010-11-22 23:56 ` Chris Wright
2010-11-23 0:24 ` Anthony Liguori
2010-11-23 6:35 ` Avi Kivity [this message]
2010-11-23 6:41 ` [Qemu-devel] " Avi Kivity
2010-11-23 8:16 ` Dor Laor
2010-11-23 13:57 ` Anthony Liguori
2010-11-23 13:51 ` Anthony Liguori
2010-11-23 14:00 ` Avi Kivity
2010-11-23 14:24 ` Anthony Liguori
2010-11-23 14:35 ` Avi Kivity
2010-11-23 7:29 ` 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=4CEB6097.2030203@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=chrisw@sous-sol.org \
--cc=kvm@vger.kernel.org \
--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