From: Dario Faggioli <raistlin@linux.it>
To: Igor Druzhinin <igor.druzhinin@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
Kevin Tian <kevin.tian@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anshul Makkar <anshul.makkar@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 1/2] VMX: fix VMCS race on context-switch paths
Date: Thu, 09 Nov 2017 10:54:51 +0100 [thread overview]
Message-ID: <1510221291.4517.170.camel@linux.it> (raw)
In-Reply-To: <c1e82778-6730-e5c8-b738-dec50f374dbc@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1855 bytes --]
On Tue, 2017-11-07 at 14:24 +0000, Igor Druzhinin wrote:
> Perhaps I should improve my diagram:
>
> pCPU1: vCPUx of domain X -> migrate to pCPU2 -> switch to idle
> context
> -> RCU callbacks -> vcpu_destroy(vCPUy of domain Y) ->
> vmx_vcpu_disable_pml() -> vmx_vmcs_clear() (VMCS is trashed at this
> point on pCPU1)
>
> pCPU2: context switch into vCPUx -> vCPUx.is_running = 1 -> TLB flush
> from context switch to clean TLB on pCPU1
>
Sorry, there must be something I'm missing (or misunderstanding).
What is this code that checks is_running and triggers the TLB flush?
But, more important, how come you are context switching to something
that has is_running == 1 ? That should not be possible.
In fact, from a scheduling code perspective, since you're mentioning
vCPU migration between pCPUs:
pCPU1
.
.
//vCPUx->is_running is 1
vCPUx->pause_flags |= _VPF_migrating
schedule()
idle->is_running = 1
//vCPUx->pause_flags != 0 ==> it's blocked and can't be scheduled!
context_switch( prev=vCPUx, next=idle )
set_current( idle )
//let's be lazy! don't call __context_switch()
context_saved( vCPUx )
vCPUx->is_running = 0
SCHED_OP( context_saved ) //NULL for Credit1
vcpu_migrate( vCPUx )
if ( vCPUx->is_running || !test_and_clear(_VPF_migrating) )
return;
vcpu_wake( vCPUx )
.
.
.
So, basically, the scheduler on pCPU2 can decide to pick vCPUx from the
runqueue and switch to it _only_ if it has gone through vcpu_wake(),
which must actually have woken up it, which happens if _VPF_migrating
has been cleared, which means is_running was 0 already.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-09 9:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 11:10 [PATCH v2 0/2] x86: context switch handling adjustments Jan Beulich
2017-02-16 11:15 ` [PATCH v2 1/2] VMX: fix VMCS race on context-switch paths Jan Beulich
2017-02-16 12:27 ` Andrew Cooper
2017-02-16 12:35 ` Jan Beulich
2017-02-17 3:48 ` Tian, Kevin
2017-02-17 8:40 ` Sergey Dyasli
2017-02-17 9:01 ` Jan Beulich
2017-10-27 17:42 ` Igor Druzhinin
2017-11-02 19:46 ` Igor Druzhinin
2017-11-07 8:07 ` Jan Beulich
2017-11-07 14:24 ` Igor Druzhinin
2017-11-07 14:55 ` Jan Beulich
2017-11-07 15:52 ` Igor Druzhinin
2017-11-07 16:31 ` Jan Beulich
2017-11-09 10:05 ` Jan Beulich
2017-11-09 10:36 ` Dario Faggioli
2017-11-09 12:58 ` Jan Beulich
2017-11-09 9:54 ` Dario Faggioli [this message]
2017-11-09 10:17 ` Jan Beulich
2017-11-09 10:36 ` Sergey Dyasli
2017-11-09 11:01 ` Dario Faggioli
2017-11-09 13:08 ` Jan Beulich
2017-11-09 14:16 ` Dario Faggioli
2017-11-09 14:39 ` Jan Beulich
2017-11-09 16:38 ` Jan Beulich
2017-11-09 10:39 ` Dario Faggioli
2017-11-07 15:16 ` Jan Beulich
2017-02-16 11:16 ` [PATCH v2 2/2] x86: package up context switch hook pointers Jan Beulich
2017-02-16 11:23 ` Andrew Cooper
2017-02-17 3:49 ` Tian, Kevin
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=1510221291.4517.170.camel@linux.it \
--to=raistlin@linux.it \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=igor.druzhinin@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=sergey.dyasli@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).