From: Anthony Liguori <aliguori@linux.vnet.ibm.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: [PATCH] qemu-kvm: introduce cpu_start/cpu_stop commands
Date: Mon, 22 Nov 2010 17:44:44 -0600 [thread overview]
Message-ID: <4CEB006C.8010407@linux.vnet.ibm.com> (raw)
In-Reply-To: <20101122230405.GB10050@sequoia.sous-sol.org>
On 11/22/2010 05:04 PM, 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.
>
Time skew is a big topic. Are you talking about TSC drift, pit/rtc/hpet
drift, etc?
It's certainly going to stress periodic interrupt catch up code.
Regards,
Anthony Liguori
> thanks,
> -chris
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] qemu-kvm: introduce cpu_start/cpu_stop commands
Date: Mon, 22 Nov 2010 17:44:44 -0600 [thread overview]
Message-ID: <4CEB006C.8010407@linux.vnet.ibm.com> (raw)
In-Reply-To: <20101122230405.GB10050@sequoia.sous-sol.org>
On 11/22/2010 05:04 PM, 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.
>
Time skew is a big topic. Are you talking about TSC drift, pit/rtc/hpet
drift, etc?
It's certainly going to stress periodic interrupt catch up code.
Regards,
Anthony Liguori
> thanks,
> -chris
>
next prev parent reply other threads:[~2010-11-22 23:44 UTC|newest]
Thread overview: 29+ 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:00 ` [Qemu-devel] " Anthony Liguori
2010-11-22 23:03 ` Anthony Liguori
2010-11-22 23:03 ` [Qemu-devel] " Anthony Liguori
2010-11-22 23:04 ` Chris Wright
2010-11-22 23:04 ` [Qemu-devel] " Chris Wright
2010-11-22 23:44 ` Anthony Liguori [this message]
2010-11-22 23:44 ` Anthony Liguori
2010-11-22 23:56 ` Chris Wright
2010-11-22 23:56 ` [Qemu-devel] " Chris Wright
2010-11-23 0:24 ` Anthony Liguori
2010-11-23 0:24 ` [Qemu-devel] " Anthony Liguori
2010-11-23 6:35 ` Avi Kivity
2010-11-23 6:41 ` [Qemu-devel] " Avi Kivity
2010-11-23 6:41 ` Avi Kivity
2010-11-23 8:16 ` Dor Laor
2010-11-23 8:16 ` Dor Laor
2010-11-23 13:57 ` Anthony Liguori
2010-11-23 13:57 ` Anthony Liguori
2010-11-23 13:51 ` Anthony Liguori
2010-11-23 13:51 ` Anthony Liguori
2010-11-23 14:00 ` Avi Kivity
2010-11-23 14:00 ` Avi Kivity
2010-11-23 14:24 ` Anthony Liguori
2010-11-23 14:24 ` Anthony Liguori
2010-11-23 14:35 ` Avi Kivity
2010-11-23 14:35 ` Avi Kivity
2010-11-23 7:29 ` Gleb Natapov
2010-11-23 7:29 ` [Qemu-devel] " 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=4CEB006C.8010407@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.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 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.