On Tue, Feb 10, 2015 at 01:00:35PM -0800, Andy Lutomirski wrote:
> On Tue, Feb 10, 2015 at 12:42 PM, Paul E. McKenney
> wrote:
> > On Tue, Feb 10, 2015 at 12:19:28PM -0800, Andy Lutomirski wrote:
> >> On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
> >> wrote:
> >> > On Tue, Feb 10, 2015 at
On Tue, Feb 10, 2015 at 12:42 PM, Paul E. McKenney
wrote:
> On Tue, Feb 10, 2015 at 12:19:28PM -0800, Andy Lutomirski wrote:
>> On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
>> wrote:
>> > On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
>> >> On 02/10/2015 06:41 AM,
On Tue, Feb 10, 2015 at 12:19:28PM -0800, Andy Lutomirski wrote:
> On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
> wrote:
> > On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
> >> On 02/10/2015 06:41 AM, r...@redhat.com wrote:
> >> >From: Rik van Riel
> >> >
> >> >The host
On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
wrote:
> On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
>> On 02/10/2015 06:41 AM, r...@redhat.com wrote:
>> >From: Rik van Riel
>> >
>> >The host kernel is not doing anything while the CPU is executing
>> >a KVM guest VCPU, so
On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
> On 02/10/2015 06:41 AM, r...@redhat.com wrote:
> >From: Rik van Riel
> >
> >The host kernel is not doing anything while the CPU is executing
> >a KVM guest VCPU, so it can be marked as being in an extended
> >quiescent state,
On 02/10/2015 02:59 PM, Andy Lutomirski wrote:
> On 02/10/2015 06:41 AM, r...@redhat.com wrote:
>> From: Rik van Riel
>>
>> The host kernel is not doing anything while the CPU is executing
>> a KVM guest VCPU, so it can be marked as being in an extended
>> quiescent state, identical to that used
On 02/10/2015 06:41 AM, r...@redhat.com wrote:
From: Rik van Riel
The host kernel is not doing anything while the CPU is executing
a KVM guest VCPU, so it can be marked as being in an extended
quiescent state, identical to that used when running user space
code.
The only exception to that
On Tue, Feb 10, 2015 at 01:00:35PM -0800, Andy Lutomirski wrote:
On Tue, Feb 10, 2015 at 12:42 PM, Paul E. McKenney
paul...@linux.vnet.ibm.com wrote:
On Tue, Feb 10, 2015 at 12:19:28PM -0800, Andy Lutomirski wrote:
On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
On Tue, Feb 10, 2015 at 12:42 PM, Paul E. McKenney
paul...@linux.vnet.ibm.com wrote:
On Tue, Feb 10, 2015 at 12:19:28PM -0800, Andy Lutomirski wrote:
On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
paul...@linux.vnet.ibm.com wrote:
On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski
On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
paul...@linux.vnet.ibm.com wrote:
On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
On 02/10/2015 06:41 AM, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
The host kernel is not doing anything while the CPU is
On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
On 02/10/2015 06:41 AM, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
The host kernel is not doing anything while the CPU is executing
a KVM guest VCPU, so it can be marked as being in an extended
quiescent state,
On 02/10/2015 06:41 AM, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
The host kernel is not doing anything while the CPU is executing
a KVM guest VCPU, so it can be marked as being in an extended
quiescent state, identical to that used when running user space
code.
The only
On 02/10/2015 02:59 PM, Andy Lutomirski wrote:
On 02/10/2015 06:41 AM, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
The host kernel is not doing anything while the CPU is executing
a KVM guest VCPU, so it can be marked as being in an extended
quiescent state, identical to that
On Tue, Feb 10, 2015 at 12:19:28PM -0800, Andy Lutomirski wrote:
On Tue, Feb 10, 2015 at 12:14 PM, Paul E. McKenney
paul...@linux.vnet.ibm.com wrote:
On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
On 02/10/2015 06:41 AM, r...@redhat.com wrote:
From: Rik van Riel
14 matches
Mail list logo