linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <kernellwp@gmail.com>
To: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org,
	virtualization@lists.linux-foundation.org,
	linux-s390 <linux-s390@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	mpe@ellerman.id.au, Paul Mackerras <paulus@samba.org>,
	benh@kernel.crashing.org,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Waiman Long <waiman.long@hpe.com>,
	will.deacon@arm.com, boqun.feng@gmail.com,
	Davidlohr Bueso <dave@stgolabs.net>,
	schwidefsky@de.ibm.com
Subject: Re: [PATCH v2 2/4] powerpc/spinlock: support vcpu preempted check
Date: Tue, 5 Jul 2016 17:57:56 +0800	[thread overview]
Message-ID: <CANRm+CxQMSrg69p2Xey829Mz4Au9YCai+4JD17i9urdbj0VgkQ@mail.gmail.com> (raw)
In-Reply-To: <1467124991-13164-3-git-send-email-xinhui.pan@linux.vnet.ibm.com>

Hi Xinhui,
2016-06-28 22:43 GMT+08:00 Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>:
> This is to fix some lock holder preemption issues. Some other locks
> implementation do a spin loop before acquiring the lock itself. Currently
> kernel has an interface of bool vcpu_is_preempted(int cpu). It take the cpu
> as parameter and return true if the cpu is preempted. Then kernel can break
> the spin loops upon on the retval of vcpu_is_preempted.
>
> As kernel has used this interface, So lets support it.
>
> Only pSeries need supoort it. And the fact is powerNV are built into same
> kernel image with pSeries. So we need return false if we are runnig as
> powerNV. The another fact is that lppaca->yiled_count keeps zero on
> powerNV. So we can just skip the machine type.

Lock holder vCPU preemption can be detected by hardware pSeries or
paravirt method?

Regards,
Wanpeng Li

  reply	other threads:[~2016-07-05  9:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 14:43 [PATCH v2 0/4] implement vcpu preempted check Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 1/4] kernel/sched: introduce vcpu preempted check interface Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 2/4] powerpc/spinlock: support vcpu preempted check Pan Xinhui
2016-07-05  9:57   ` Wanpeng Li [this message]
2016-07-06  4:58     ` xinhui
2016-07-06  6:46       ` Wanpeng Li
2016-07-06  7:58         ` Peter Zijlstra
2016-07-06  8:32           ` Wanpeng Li
2016-07-06 10:18             ` xinhui
2016-07-06 10:54   ` Balbir Singh
2016-07-15 15:35     ` Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 3/4] locking/osq: Drop the overload of osq_lock() Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 4/4] kernel/locking: Drop the overload of {mutex, rwsem}_spin_on_owner Pan Xinhui
2016-07-06  6:52 ` [PATCH v2 0/4] implement vcpu preempted check Peter Zijlstra
2016-07-06  7:47   ` Juergen Gross
2016-07-06  8:19     ` Peter Zijlstra
2016-07-06  8:38       ` Juergen Gross
2016-07-06 12:44       ` Paolo Bonzini
2016-07-06 16:56       ` Christian Borntraeger
2016-07-06 10:05   ` xinhui
2016-07-06 10:44   ` Paolo Bonzini
2016-07-06 11:59     ` Peter Zijlstra
2016-07-06 12:08     ` Wanpeng Li
2016-07-06 12:28       ` Paolo Bonzini
2016-07-06 13:03         ` Wanpeng Li
2016-07-07  8:48         ` Wanpeng Li
2016-07-07  9:42           ` Peter Zijlstra
2016-07-07 10:12             ` Wanpeng Li
2016-07-07 10:27               ` Wanpeng Li
2016-07-07 11:15                 ` Peter Zijlstra
2016-07-07 11:08               ` Peter Zijlstra
2016-07-07 11:09             ` Peter Zijlstra
2016-07-07 11:21             ` Peter Zijlstra
2016-07-11 15:10   ` Waiman Long
2016-07-12  4:16     ` Juergen Gross
2016-07-12 18:16       ` Waiman Long

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=CANRm+CxQMSrg69p2Xey829Mz4Au9YCai+4JD17i9urdbj0VgkQ@mail.gmail.com \
    --to=kernellwp@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=boqun.feng@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=waiman.long@hpe.com \
    --cc=will.deacon@arm.com \
    --cc=xinhui.pan@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).