On Mon, Nov 22, 2010 at 05:00:18PM -0600, Anthony Liguori 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.
>
> The purpose of these commands are to implem
On 11/23/2010 01:04 AM, Chris Wright wrote:
* Anthony Liguori (aligu...@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 SIGSTO
On 11/22/2010 05:56 PM, Chris Wright wrote:
* Anthony Liguori (aligu...@linux.vnet.ibm.com) wrote:
On 11/22/2010 05:04 PM, Chris Wright wrote:
* Anthony Liguori (aligu...@us.ibm.com) wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching
them to
* Anthony Liguori (aligu...@linux.vnet.ibm.com) wrote:
> On 11/22/2010 05:04 PM, Chris Wright wrote:
> >* Anthony Liguori (aligu...@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 comma
On 11/22/2010 05:04 PM, Chris Wright wrote:
* Anthony Liguori (aligu...@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 SIGST
* Anthony Liguori (aligu...@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
On 11/22/2010 05:00 PM, Anthony Liguori 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.
The purpose of these commands are to implement CPU hard limits using an
