From: Peter Zijlstra <peterz@infradead•org>
To: Wanpeng Li <kernellwp@gmail•com>
Cc: Paolo Bonzini <pbonzini@redhat•com>,
Pan Xinhui <xinhui.pan@linux•vnet.ibm.com>,
linux-s390 <linux-s390@vger•kernel.org>,
Davidlohr Bueso <dave@stgolabs•net>,
mpe@ellerman•id.au, boqun.feng@gmail•com, will.deacon@arm•com,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Waiman Long <waiman.long@hpe•com>,
virtualization@lists•linux-foundation.org,
Ingo Molnar <mingo@redhat•com>, Paul Mackerras <paulus@samba•org>,
benh@kernel•crashing.org, schwidefsky@de•ibm.com,
Paul McKenney <paulmck@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org, kvm <kvm@vger•kernel.org>
Subject: Re: [PATCH v2 0/4] implement vcpu preempted check
Date: Thu, 7 Jul 2016 13:08:01 +0200 [thread overview]
Message-ID: <20160707110801.GU30921@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CANRm+CyrPbOVpJ6-Wa=g6oXTU0vVfw-ciLgm-duZeVF6MBH=RA@mail.gmail.com>
On Thu, Jul 07, 2016 at 06:12:51PM +0800, Wanpeng Li wrote:
> Btw, do this in preemption
> notifier means that the vCPU is real preempted on host, however,
> depends on vmexit is different semantic I think.
Not sure; suppose the vcpu is about to reenter, eg, we're in
vcpu_enter_guest() but before the preempt_disable() and the thread gets
preempted. Are we then not preempted? The vcpu might still very much be
in running state but had to service an vmexit due to an MSR or IO port
or whatnot.
next prev parent reply other threads:[~2016-07-07 11:08 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
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 [this message]
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=20160707110801.GU30921@twins.programming.kicks-ass.net \
--to=peterz@infradead$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=boqun.feng@gmail$(echo .)com \
--cc=dave@stgolabs$(echo .)net \
--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=schwidefsky@de$(echo .)ibm.com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
--cc=waiman.long@hpe$(echo .)com \
--cc=will.deacon@arm$(echo .)com \
--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