public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead•org>
To: Pan Xinhui <xinhui.pan@linux•vnet.ibm.com>
Cc: linux-kernel@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
	virtualization@lists•linux-foundation.org,
	linux-s390@vger•kernel.org,
	xen-devel-request@lists•xenproject.org, kvm@vger•kernel.org,
	benh@kernel•crashing.org, paulus@samba•org, mpe@ellerman•id.au,
	mingo@redhat•com, paulmck@linux•vnet.ibm.com,
	will.deacon@arm•com, kernellwp@gmail•com, jgross@suse•com,
	pbonzini@redhat•com, bsingharora@gmail•com, boqun.feng@gmail•com,
	borntraeger@de•ibm.com, rkrcmar@redhat•com
Subject: Re: [PATCH v5 0/9] implement vcpu preempted check
Date: Fri, 21 Oct 2016 07:40:50 +0200	[thread overview]
Message-ID: <20161021054050.GX3102@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1476998874-2089-1-git-send-email-xinhui.pan@linux.vnet.ibm.com>

On Thu, Oct 20, 2016 at 05:27:45PM -0400, Pan Xinhui wrote:

> 
> This patch set aims to fix lock holder preemption issues.

Thanks, this looks very good. I'll wait for ACKs from at least the KVM
people, since that was I think the most contentious patch.

      parent reply	other threads:[~2016-10-21  5:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 21:27 [PATCH v5 0/9] implement vcpu preempted check Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 1/9] kernel/sched: introduce vcpu preempted check interface Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 2/9] locking/osq: Drop the overload of osq_lock() Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 3/9] kernel/locking: Drop the overload of {mutex, rwsem}_spin_on_owner Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 4/9] powerpc/spinlock: support vcpu preempted check Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 5/9] x86, paravirt: Add interface to support kvm/xen " Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 6/9] x86, kvm: support " Pan Xinhui
2016-10-24  8:08   ` xinhui
2016-10-20 21:27 ` [PATCH v5 7/9] x86, xen: " Pan Xinhui
2016-10-21  5:08   ` Juergen Gross
2016-10-20 21:27 ` [PATCH v5 8/9] s390/spinlock: Provide vcpu_is_preempted Pan Xinhui
2016-10-20 21:27 ` [PATCH v5 9/9] Documentation: virtual: kvm: Support vcpu preempted check Pan Xinhui
2016-10-21  1:23   ` Boqun Feng
2016-10-21  1:42     ` Pan Xinhui
2016-10-21 11:27   ` David Laight
2016-10-21 18:39     ` rkrcmar
2016-10-24  2:46       ` xinhui
2016-10-24 14:42       ` Paolo Bonzini
2016-10-24 15:05         ` rkrcmar
2016-10-24  2:44     ` xinhui
2016-10-24  8:12   ` xinhui
2016-10-21  5:40 ` Peter Zijlstra [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=20161021054050.GX3102@twins.programming.kicks-ass.net \
    --to=peterz@infradead$(echo .)org \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=boqun.feng@gmail$(echo .)com \
    --cc=borntraeger@de$(echo .)ibm.com \
    --cc=bsingharora@gmail$(echo .)com \
    --cc=jgross@suse$(echo .)com \
    --cc=kernellwp@gmail$(echo .)com \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-s390@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mingo@redhat$(echo .)com \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=paulmck@linux$(echo .)vnet.ibm.com \
    --cc=paulus@samba$(echo .)org \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=rkrcmar@redhat$(echo .)com \
    --cc=virtualization@lists$(echo .)linux-foundation.org \
    --cc=will.deacon@arm$(echo .)com \
    --cc=xen-devel-request@lists$(echo .)xenproject.org \
    --cc=xinhui.pan@linux$(echo .)vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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