From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Pan Xinhui <xinhui@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
xen-devel-request@lists.xenproject.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
Subject: Re: [PATCH v2 1/1] s390/spinlock: Provide vcpu_is_preempted
Date: Fri, 30 Sep 2016 12:29:50 +0200 [thread overview]
Message-ID: <d4beac12-5be3-32ed-28d5-82fc2f79143b@de.ibm.com> (raw)
In-Reply-To: <b2ace794-c1cc-11be-f9f5-d6429e192825@linux.vnet.ibm.com>
On 09/30/2016 06:49 AM, Pan Xinhui wrote:
>
> but I can't help thinking that if this is a!SMP system, maybe we could only
> #ifndef CONFIG_SMP
> static inline bool arch_vcpu_is_preempted(int cpu) { return false; }
> #else
Yes, I will add that to v3. Thanks for spotting.
next prev parent reply other threads:[~2016-09-30 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 15:51 [PATCH v2 0/1] s390 preparation for vcpu preempted check Christian Borntraeger
2016-09-29 15:51 ` [PATCH v2 1/1] s390/spinlock: Provide vcpu_is_preempted Christian Borntraeger
2016-09-30 4:49 ` Pan Xinhui
2016-09-30 5:52 ` Boqun Feng
2016-09-30 6:35 ` Pan Xinhui
2016-10-04 10:17 ` Christian Borntraeger
2016-09-30 10:29 ` Christian Borntraeger [this message]
2016-10-19 6:56 ` Christian Borntraeger
2016-10-19 7:44 ` Heiko Carstens
2016-10-19 8:42 ` [PATCH v3] " Christian Borntraeger
2016-10-19 8:50 ` Heiko Carstens
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=d4beac12-5be3-32ed-28d5-82fc2f79143b@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jgross@suse.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=xen-devel-request@lists.xenproject.org \
--cc=xinhui.pan@linux.vnet.ibm.com \
--cc=xinhui@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
all inboxes | Powered by JetHome®