xen/wait: Improvements
cover xen/wait: Improvements
This started out as patch 2 for a different task, and quickly identified some technical debt, long overdue for cleaning up.
Andrew Cooper (5):
xen/wait: Drop vestigial remnants of TRAP_regs_partial xen/wait: Extend the description of how this logic actually works xen/wait: Minor asm improvements
xen/wait: Use relative stack adjustments
xen/wait: Remove VCPU_AFFINITY_WAIT
xen/common/domain.c | 2 - xen/common/sched/core.c | 4 +- xen/common/wait.c | 117 +++++++++++++++++++++++++----------------------- xen/include/xen/sched.h | 1 - 4 files changed, 63 insertions(+), 61 deletions(-)
Signature · 1 line
2.11.0
PATCH 1/5 xen/wait: Drop vestigial remnants of TRAP_regs_partial
The preservation of entry_vector was introduced with ecf9846a6a20 ("x86:
save/restore only partial register state where possible") where TRAP_regs_partial was introduced, but missed from f9eb74789af7 ("x86/entry:
Remove support for partial cpu_user_regs frames") where TRAP_regs_partial was removed.
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
--- xen/common/wait.c | 3 --- 1 file changed, 3 deletions(-)
xen/common/wait.c +0 -3
@@ -124,7 +124,6 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)struct cpu_info *cpu_info =get_cpu_info ();struct vcpu *curr = current;unsigned long dummy; -u32 entry_vector = cpu_info->guest_cpu_user_regs.entry_vector;ASSERT (wqv->esp ==0 );
@@ -169,8 +168,6 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)for ( ; ; )do_softirq (); } - - cpu_info->guest_cpu_user_regs.entry_vector = entry_vector; }static void __finish_wait (struct waitqueue_vcpu *wqv)
Signature · 1 line
2.11.0
Re: [PATCH 1/5] xen/wait: Drop vestigial remnants of TRAP_regs_partial
Quoted 8 lines · Andrew Cooper
The preservation of
entry_vectorwas introduced withecf9846a6a20("x86:
save/restore only partial register state where possible") whereTRAP_regs_partialwas introduced, but missed fromf9eb74789af7("x86/entry:
Remove support for partialcpu_user_regsframes") whereTRAP_regs_partialwas removed.Fixes f9eb74789af7 ("x86/entry: Remove support for partial cpu_user_regs frames")Signed-off-by Andrew Cooper <[email protected]>
PATCH 2/5 xen/wait: Extend the description of how this logic actually works
In reply to Andrew Cooper---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
--- xen/common/wait.c | 29 +++++++++++++++++++++++++---- 1 file changed, 25 insertions(+), 4 deletions(-)
xen/common/wait.c +25 -4
@@ -137,7 +137,19 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)do_softirq (); } -/* Hand-rolled setjmp(). */ +/* +* Hand-rolled setjmp(). +* +* __prepare_to_wait() is the leaf of a deep calltree. Preserve the GPRs, +* bounds check what we want to stash in wqv->stack, copy the active stack +* (up to cpu_info) into wqv->stack, then return normally. Our caller +* will shortly schedule() and discard the current context. +* +* The copy out is performed with a rep movsb. When +* check_wakeup_from_wait() longjmp()'s back into us, %rsp is pre-adjusted +* to be suitable and %rsi/%rdi are swapped, so the rep movsb instead +* copies in from wqv->stack over the active stack. +*/ asmvolatile ("push %%rax; push %%rbx; push %%rdx; push %%rbp;" "push %%r8; push %%r9; push %%r10; push %%r11;"
@@ -199,9 +211,18 @@ void check_wakeup_from_wait(void) }/* -* Hand-rolled longjmp(). Returns to __prepare_to_wait(), and lands on a -* `rep movs` instruction. All other GPRs are restored from the stack, so -* are available for use here. +* Hand-rolled longjmp(). +* +* check_wakeup_from_wait() is always called with a shallow stack, +* immediately after the vCPU has been rescheduled. +* +* Adjust %rsp to be the correct depth for the (deeper) stack we want to +* restore, then prepare %rsi, %rdi and %rcx such that when we intercept +* the rep movs in __prepare_to_wait(), it copies from wqv->stack over the +* active stack. +* +* All other GPRs are available for use; they're either restored from +* wqv->stack or explicitly clobbered. */ asmvolatile ( "mov %1,%%"__OP"sp; jmp .L_wq_resume;"
Signature · 1 line
2.11.0
Re: [PATCH 2/5] xen/wait: Extend the description of how this logic actually works
Quoted 6 lines · Andrew Cooper
xen/common/wait.c +0
-2@@ -199,9 +211,18 @@ void check_wakeup_from_wait(void) }/* -* Hand-rolled longjmp(). Returns to __prepare_to_wait(), and lands on a -* `rep movs` instruction. All other GPRs are restored from the stack, so
xen/common/wait.c void check_wakeup_from_wait(void) · line 222
Quoted 10 lines
xen/common/wait.c +9
-1-* are available for use here. +* Hand-rolled longjmp(). +* +* check_wakeup_from_wait() is always called with a shallow stack, +* immediately after the vCPU has been rescheduled. +* +* Adjust %rsp to be the correct depth for the (deeper) stack we want to +* restore, then prepare %rsi, %rdi and %rcx such that when we intercept +* the rep movs in __prepare_to_wait(), it copies from wqv->stack over the +* active stack.
I'm struggling with the use of "intercept" here, but I guess that's just because I'm not a native speaker.
xen/common/wait.c void check_wakeup_from_wait(void) · line 225
Quoted 2 lines
xen/common/wait.c +2
-0+* All other GPRs are available for use; they're either restored from +* wqv->stack or explicitly clobbered.
You talking of "other GPRs" - there aren't any which are explicitly clobbered. It's only the previously named ones which are. Hence I'd like to ask that the respective parts of the sentence be dropped. Then
Jan
Re: [PATCH 2/5] xen/wait: Extend the description of how this logic actually works
Quoted 4 lines · Jan Beulich
Quoted 3 lines · Andrew Cooper
(quoted diff) +0
-0@@ -199,9 +211,18 @@ void check_wakeup_from_wait(void) }
Quoted 15 lines
xen/common/wait.c void check_wakeup_from_wait(void) · line 222
Quoted 13 lines
xen/common/wait.c +9
-3/* -* Hand-rolled longjmp(). Returns to __prepare_to_wait(), and lands on a -* `rep movs` instruction. All other GPRs are restored from the stack, so -* are available for use here. +* Hand-rolled longjmp(). +* +* check_wakeup_from_wait() is always called with a shallow stack, +* immediately after the vCPU has been rescheduled. +* +* Adjust %rsp to be the correct depth for the (deeper) stack we want to +* restore, then prepare %rsi, %rdi and %rcx such that when we intercept +* the rep movs in __prepare_to_wait(), it copies from wqv->stack over the +* active stack. I'm struggling with the use of "intercept" here, but I guess that's just because I'm not a native speaker.
"intercept" is the same terminology used in the middle of __prepare_to_wait()'s block.
It's because we have a weird setup where this is (now) a noreturn function merging into the middle of a function which already executed once.
I'm happy to change it if it's unclear, but I can't think of a better description.
Quoted 6 lines
xen/common/wait.c void check_wakeup_from_wait(void) · line 225
Quoted 2 lines
xen/common/wait.c +2
-0+* All other GPRs are available for use; they're either restored from +* wqv->stack or explicitly clobbered. You talking of "other GPRs" - there aren't any which are explicitly clobbered. It's only the previously named ones which are. Hence I'd like to ask that the respective parts of the sentence be dropped. Then
Reviewed-by Jan Beulich <[email protected]>
It becomes true in the next patch. I'll try and shuffle things.
~Andrew
Re: [PATCH 2/5] xen/wait: Extend the description of how this logic actually works
Quoted 21 lines · Andrew Cooper
Quoted 4 lines · Jan Beulich
Quoted 3 lines · Andrew Cooper
(quoted diff) +0
-0@@ -199,9 +211,18 @@ void check_wakeup_from_wait(void) }Quoted 15 lines
xen/common/wait.c void check_wakeup_from_wait(void) · line 222
Quoted 13 lines
xen/common/wait.c +9
-3/* -* Hand-rolled longjmp(). Returns to __prepare_to_wait(), and lands on a -* `rep movs` instruction. All other GPRs are restored from the stack, so -* are available for use here. +* Hand-rolled longjmp(). +* +* check_wakeup_from_wait() is always called with a shallow stack, +* immediately after the vCPU has been rescheduled. +* +* Adjust %rsp to be the correct depth for the (deeper) stack we want to +* restore, then prepare %rsi, %rdi and %rcx such that when we intercept +* the rep movs in __prepare_to_wait(), it copies from wqv->stack over the +* active stack. I'm struggling with the use of "intercept" here, but I guess that's just because I'm not a native speaker.
Quoted 8 lines
"intercept" is the same terminology used in the middle of __prepare_to_wait()'s block.
It's because we have a weird setup where this is (now) a noreturn function merging into the middle of a function which already executed once.
I'm happy to change it if it's unclear, but I can't think of a better description.
"... when we go back to ..."? (But I'm not meaning to insist on a wording change.)
Jan
PATCH 3/5 xen/wait: Minor asm improvements
In reply to Andrew CooperThere is no point preserving all registers. Instead, preserve an arbitrary 6 registers, and list the rest as clobbered. This does not alter the register scheduling at all, but does reduce the amount of state needing saving.
Use a named parameter for page size, instead of needing to parse which is parameter 3. Adjust the formatting of the parameters slightly to simply the diff of the subsequent patch.
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
--- xen/common/wait.c | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-)
xen/common/wait.c +15 -15
@@ -151,13 +151,12 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)* copies in from wqv->stack over the active stack. */ asmvolatile ( -"push %%rax; push %%rbx; push %%rdx; push %%rbp;" -"push %%r8; push %%r9; push %%r10; push %%r11;" -"push %%r12; push %%r13; push %%r14; push %%r15;" +"push %%rbx; push %%rbp; push %%r12;" +"push %%r13; push %%r14; push %%r15;" "sub %%esp,%%ecx;" -"cmp %3,%%ecx;" -"ja .L_skip;" +"cmp %[sz], %%ecx;" +"ja .L_skip;" /* Bail if >4k */ "mov %%rsp,%%rsi;" /* check_wakeup_from_wait() longjmp()'s to this point. */
@@ -165,12 +164,12 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv) "mov %%rsp,%%rsi;" ".L_skip:" -"pop %%r15; pop %%r14; pop %%r13; pop %%r12;" -"pop %%r11; pop %%r10; pop %%r9; pop %%r8;" -"pop %%rbp; pop %%rdx; pop %%rbx; pop %%rax" + "pop %%r15; pop %%r14; pop %%r13;" + "pop %%r12; pop %%rbp; pop %%rbx;" : "=&S" (wqv->esp), "=&c" (dummy), "=&D" (dummy) - : "i" (PAGE_SIZE), "0" (0), "1" (cpu_info), "2" (wqv->stack) - : "memory" ); + : "0" (0), "1" (cpu_info), "2" (wqv->stack), + [sz] "i" (PAGE_SIZE) + : "memory", "rax", "rdx", "r8", "r9", "r10", "r11" );if (unlikely (wqv->esp ==0 ) ) {
@@ -224,11 +223,12 @@ void check_wakeup_from_wait(void)* All other GPRs are available for use; they're either restored from * wqv->stack or explicitly clobbered. */ - asmvolatile ( -"mov %1,%%" __OP"sp; jmp .L_wq_resume;" - : :"S" (wqv->stack),"D" (wqv->esp), -"c" ((char *)get_cpu_info () - (char *)wqv->esp) - :"memory" ); + asmvolatile ("mov %%rdi, %%rsp;" +"jmp .L_wq_resume;" + : + :"S" (wqv->stack),"D" (wqv->esp), +"c" ((char *)get_cpu_info () - (char *)wqv->esp) + :"memory" );unreachable (); }
Signature · 1 line
2.11.0
Re: [PATCH 3/5] xen/wait: Minor asm improvements
Quoted 39 lines · Andrew Cooper
xen/common/wait.c +9
-10@@ -151,13 +151,12 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)* copies in from wqv->stack over the active stack. */ asmvolatile ( -"push %%rax; push %%rbx; push %%rdx; push %%rbp;" -"push %%r8; push %%r9; push %%r10; push %%r11;" -"push %%r12; push %%r13; push %%r14; push %%r15;" +"push %%rbx; push %%rbp; push %%r12;" +"push %%r13; push %%r14; push %%r15;" "sub %%esp,%%ecx;" -"cmp %3,%%ecx;" -"ja .L_skip;" +"cmp %[sz], %%ecx;" +"ja .L_skip;" /* Bail if >4k */ "mov %%rsp,%%rsi;" /* check_wakeup_from_wait() longjmp()'s to this point. */@@ -165,12 +164,12 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv) "mov %%rsp,%%rsi;" ".L_skip:" -"pop %%r15; pop %%r14; pop %%r13; pop %%r12;" -"pop %%r11; pop %%r10; pop %%r9; pop %%r8;" -"pop %%rbp; pop %%rdx; pop %%rbx; pop %%rax" + "pop %%r15; pop %%r14; pop %%r13;" + "pop %%r12; pop %%rbp; pop %%rbx;" : "=&S" (wqv->esp), "=&c" (dummy), "=&D" (dummy) - : "i" (PAGE_SIZE), "0" (0), "1" (cpu_info), "2" (wqv->stack) - : "memory" ); + : "0" (0), "1" (cpu_info), "2" (wqv->stack), + [sz] "i" (PAGE_SIZE) + : "memory", "rax", "rdx", "r8", "r9", "r10", "r11" );if (unlikely (wqv->esp ==0 ) ) {
xen/common/wait.c void check_wakeup_from_wait(void) · line 225
Quoted 3 lines
xen/common/wait.c +0
-0@@ -224,11 +223,12 @@ void check_wakeup_from_wait(void)* All other GPRs are available for use; they're either restored from * wqv->stack or explicitly clobbered. */
Ah, this is where the comment stops being misleading. I think it would be better if you had it correct there and adjusted it here.
xen/common/wait.c void check_wakeup_from_wait(void) · line 227
Quoted 7 lines
xen/common/wait.c +2
-5- asmvolatile ( -"mov %1,%%" __OP"sp; jmp .L_wq_resume;" - : :"S" (wqv->stack),"D" (wqv->esp), -"c" ((char *)get_cpu_info () - (char *)wqv->esp) - :"memory" ); + asmvolatile ("mov %%rdi, %%rsp;" + "jmp .L_wq_resume;"
Minor remark: No need for trailing semicolons like this one. Anyway:
Jan
PATCH 4/5 xen/wait: Use relative stack adjustments
In reply to Andrew CooperThe waitqueue's esp field is overloaded. It serves both as an indication that the waitqueue is in use, and as a direction to check_wakeup_from_wait() as to where to adjust the stack pointer to, but using an absolute pointer comes with a cost if requiring the vCPU to wake up on the same pCPU it went to sleep on.
Instead, have the waitqueue just keep track of how much data is on wqv->stack. This is no practical change in __prepare_to_wait() (it already calculated the delta) but split the result out of the (also overloaded) %rsi output parameter by using a separate register instead.
check_wakeup_from_wait() has a bit more work to do. It now needs to calculate the adjustment to %rsp rather than having the new %rsp provided as a parameter.
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
--- xen/common/wait.c | 44 ++++++++++++++++++++++++++++---------------- 1 file changed, 28 insertions(+), 16 deletions(-)
xen/common/wait.c +28 -16
@@ -32,8 +32,8 @@ struct waitqueue_vcpu {* Xen/x86 does not have per-vcpu hypervisor stacks. So we must save the * hypervisor context before sleeping (descheduling), setjmp/longjmp-style. */ -void *esp;char *stack; +unsigned int used;#endif };
@@ -121,11 +121,11 @@ void wake_up_all(struct waitqueue_head *wq)static void __prepare_to_wait (struct waitqueue_vcpu *wqv) { -struct cpu_info *cpu_info =get_cpu_info ();struct vcpu *curr = current;unsigned long dummy; +unsigned int used; -ASSERT (wqv->esp ==0 ); +ASSERT (wqv->used ==0 );/* Save current VCPU affinity; force wakeup on *this* CPU only. */ if (vcpu_temporary_affinity (curr,smp_processor_id (),VCPU_AFFINITY_WAIT ) )
@@ -154,24 +154,25 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv) "push %%rbx; push %%rbp; push %%r12;" "push %%r13; push %%r14; push %%r15;" -"sub %%esp,%%ecx;" + "sub %%esp, %%ecx;" /* ecx = delta to cpu_info */ "cmp %[sz], %%ecx;" "ja .L_skip;" /* Bail if >4k */ -"mov %%rsp,%%rsi;" + + "mov %%ecx, %%eax;" + "mov %%rsp, %%rsi;" /* Copy from the stack, into wqv->stack */ /* check_wakeup_from_wait() longjmp()'s to this point. */ ".L_wq_resume: rep movsb;" -"mov %%rsp,%%rsi;" ".L_skip:" "pop %%r15; pop %%r14; pop %%r13;" "pop %%r12; pop %%rbp; pop %%rbx;" - : "=&S" (wqv->esp), "=&c" (dummy), "=&D" (dummy) - : "0" (0), "1" (cpu_info), "2" (wqv->stack), + : "=a" (used), "=D" (dummy), "=c" (dummy), "=&S" (dummy) + : "a" (0), "D" (wqv->stack), "c" (get_cpu_info()), [sz] "i" (PAGE_SIZE) - : "memory", "rax", "rdx", "r8", "r9", "r10", "r11" ); + : "memory", "rdx", "r8", "r9", "r10", "r11" ); -if (unlikely (wqv->esp ==0 ) ) +if (unlikely (used >PAGE_SIZE ) ) {gdprintk (XENLOG_ERR ,"Stack too large in %s\n" , __func__);domain_crash (curr->domain);
@@ -179,11 +180,13 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)for ( ; ; )do_softirq (); } + + wqv->used = used; }static void __finish_wait (struct waitqueue_vcpu *wqv) { - wqv->esp =NULL ; + wqv->used =0 ;vcpu_temporary_affinity (current,NR_CPUS ,VCPU_AFFINITY_WAIT ); }
@@ -191,10 +194,11 @@ void check_wakeup_from_wait(void) {struct vcpu *curr = current;struct waitqueue_vcpu *wqv = curr->waitqueue_vcpu; +unsigned long tmp;ASSERT (list_empty (&wqv->list)); -if (likely (wqv->esp ==NULL ) ) +if (likely (!wqv->used) )return ;/* Check if we are still pinned. */
@@ -220,14 +224,22 @@ void check_wakeup_from_wait(void)* the rep movs in __prepare_to_wait(), it copies from wqv->stack over the * active stack. * +* We are also bound by __prepare_to_wait()'s output constraints, so %eax +* needs to be wqv->used. +* * All other GPRs are available for use; they're either restored from * wqv->stack or explicitly clobbered. */ - asmvolatile ("mov %%rdi, %%rsp;" + asmvolatile ("sub %%esp, %k[var];" /* var = delta to cpu_info */ +"neg %k[var];" +"add %%ecx, %k[var];" /* var = -delta + wqv->used */ + +"sub %[var], %%rsp;" /* Adjust %rsp down to make room */ +"mov %%rsp, %%rdi;" /* Copy from wqv->stack, into the stack */ "jmp .L_wq_resume;" - : - :"S" (wqv->stack),"D" (wqv->esp), -"c" ((char *)get_cpu_info () - (char *)wqv->esp) + :"=D" (tmp), [var]"=&r" (tmp) + :"S" (wqv->stack),"c" (wqv->used),"a" (wqv->used), +"[var]" (get_cpu_info ()) :"memory" );unreachable (); }
Signature · 1 line
2.11.0
Re: [PATCH 4/5] xen/wait: Use relative stack adjustments
xen/common/wait.c void wake_up_all(struct waitqueue_head *wq) · line 128
Quoted 11 lines · Andrew Cooper
xen/common/wait.c +2
-2@@ -121,11 +121,11 @@ void wake_up_all(struct waitqueue_head *wq)static void __prepare_to_wait (struct waitqueue_vcpu *wqv) { -struct cpu_info *cpu_info =get_cpu_info ();struct vcpu *curr = current;unsigned long dummy; +unsigned int used; -ASSERT (wqv->esp ==0 ); +ASSERT (wqv->used ==0 );
Minor: Use ! like you do further down?
xen/common/wait.c static void __prepare_to_wait(struct waitqueue_vcpu *wqv) · line 159
Quoted 8 lines
xen/common/wait.c +1
-1@@ -154,24 +154,25 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)"push %%rbx; push %%rbp; push %%r12;" "push %%r13; push %%r14; push %%r15;" -"sub %%esp,%%ecx;" +"sub %%esp, %%ecx;" /* ecx = delta to cpu_info */ "cmp %[sz], %%ecx;" "ja .L_skip;" /* Bail if >4k */
According to the inputs, %eax is still 0 when bailing here, so the check below won't find "used > PAGE_SIZE". I further wonder why you don't store directly into wqv->used, and go through %eax instead.
Quoted 5 lines
xen/common/wait.c +3
-1-"mov %%rsp,%%rsi;" + +"mov %%ecx, %%eax;" +"mov %%rsp, %%rsi;" /* Copy from the stack, into wqv->stack */
xen/common/wait.c static void __prepare_to_wait(struct waitqueue_vcpu *wqv) · line 170
Quoted 10 lines
xen/common/wait.c +1
-3/* check_wakeup_from_wait() longjmp()'s to this point. */ ".L_wq_resume: rep movsb;" -"mov %%rsp,%%rsi;" ".L_skip:" "pop %%r15; pop %%r14; pop %%r13;" "pop %%r12; pop %%rbp; pop %%rbx;" - : "=&S" (wqv->esp), "=&c" (dummy), "=&D" (dummy) - : "0" (0), "1" (cpu_info), "2" (wqv->stack), + : "=a" (used), "=D" (dummy), "=c" (dummy), "=&S" (dummy)
You can't validly drop & from =D and =c. If you want to stick to going through %eax, I think that one wants & added as well and ...
xen/common/wait.c static void __prepare_to_wait(struct waitqueue_vcpu *wqv) · line 171
Quoted 1 line
xen/common/wait.c +1
-0+ : "a" (0), "D" (wqv->stack), "c" (get_cpu_info()),
... the (unused) input here dropped.
Quoted 13 lines
xen/common/wait.c +5
-1@@ -220,14 +224,22 @@ void check_wakeup_from_wait(void)* the rep movs in __prepare_to_wait(), it copies from wqv->stack over the * active stack. * +* We are also bound by __prepare_to_wait()'s output constraints, so %eax +* needs to be wqv->used. +* * All other GPRs are available for use; they're either restored from * wqv->stack or explicitly clobbered. */ - asm volatile ( "mov %%rdi, %%rsp;" + asmvolatile ("sub %%esp, %k[var];" /* var = delta to cpu_info */ + "neg %k[var];"
xen/common/wait.c void check_wakeup_from_wait(void) · line 241
Quoted 10 lines
xen/common/wait.c +6
-3+ "add %%ecx, %k[var];" /* var = -delta + wqv->used */ + + "sub %[var], %%rsp;" /* Adjust %rsp down to make room */ + "mov %%rsp, %%rdi;" /* Copy from wqv->stack, into the stack */ "jmp .L_wq_resume;" - : - : "S" (wqv->stack), "D" (wqv->esp), -"c" ((char *)get_cpu_info () - (char *)wqv->esp) + : "=D" (tmp), [var] "=&r" (tmp) + : "S" (wqv->stack), "c" (wqv->used), "a" (wqv->used),
If you want to stick to going through %eax, then I think you need to make it an output here: "+a" (wqv->used), so it is clear that the register is blocked from any other use throughout the asm(). Or you could use "=&a" and copy %ecx into %eax inside the asm(). Both may cause the compiler to emit dead code updating wqv->used right after the asm(), so I think not going through %eax is the more desirable approach (but I may well be overlooking a reason why directly dealing with wqv->used in __prepare_to_wait() isn't an option).
Strictly speaking (in particular if [right now] there wasn't just a branch after updating %rdi) you also again want "=&D" here.
Jan
Re: [PATCH 4/5] xen/wait: Use relative stack adjustments
Quoted 10 lines · Jan Beulich
Quoted 9 lines · Andrew Cooper
xen/common/wait.c +3
-2-"mov %%rsp,%%rsi;" + +"mov %%ecx, %%eax;" +"mov %%rsp, %%rsi;" /* Copy from the stack, into wqv->stack */ /* check_wakeup_from_wait() longjmp()'s to this point. */ ".L_wq_resume: rep movsb;" -"mov %%rsp,%%rsi;"
Quoted 7 lines
xen/common/wait.c static void __prepare_to_wait(struct waitqueue_vcpu *wqv) · line 170
Quoted 6 lines
".L_skip:" "pop %%r15; pop %%r14; pop %%r13;" "pop %%r12; pop %%rbp; pop %%rbx;"xen/common/wait.c +1
-2- : "=&S" (wqv->esp), "=&c" (dummy), "=&D" (dummy) - : "0" (0), "1" (cpu_info), "2" (wqv->stack), + : "=a" (used), "=D" (dummy), "=c" (dummy), "=&S" (dummy)You can't validly drop & from =D and =c.
On the contrary, GCC demands it.
& is only relevant, and only permitted, when there is not an explicit input tied to the same register.
When there is an explicit input tied to the same register, of course it can't be reused for another input before being used as an output.
https://godbolt.org/z/4vWP4PKc5
~Andrew
Re: [PATCH 4/5] xen/wait: Use relative stack adjustments
Quoted 19 lines · Andrew Cooper
Quoted 10 lines · Jan Beulich
Quoted 9 lines · Andrew Cooper
xen/common/wait.c +3
-2-"mov %%rsp,%%rsi;" + +"mov %%ecx, %%eax;" +"mov %%rsp, %%rsi;" /* Copy from the stack, into wqv->stack */ /* check_wakeup_from_wait() longjmp()'s to this point. */ ".L_wq_resume: rep movsb;" -"mov %%rsp,%%rsi;" Quoted 7 lines
xen/common/wait.c static void __prepare_to_wait(struct waitqueue_vcpu *wqv) · line 170
Quoted 6 lines
".L_skip:" "pop %%r15; pop %%r14; pop %%r13;" "pop %%r12; pop %%rbp; pop %%rbx;"xen/common/wait.c +1
-2- : "=&S" (wqv->esp), "=&c" (dummy), "=&D" (dummy) - : "0" (0), "1" (cpu_info), "2" (wqv->stack), + : "=a" (used), "=D" (dummy), "=c" (dummy), "=&S" (dummy)You can't validly drop & from =D and =c.
Quoted 7 lines
On the contrary, GCC demands it.
& is only relevant, and only permitted, when there is not an explicit input tied to the same register.
When there is an explicit input tied to the same register, of course it can't be reused for another input before being used as an output.
Oh, sorry - I neglected to take into account this adding of inputs.
Jan
PATCH 5/5 xen/wait: Remove VCPU_AFFINITY_WAIT
In reply to Andrew CooperWith the waitqueue logic updated to not use an absolute stack pointer reference, the vCPU can safely be resumed anywhere.
Remove VCPU_AFFINITY_WAIT completely, getting rid of two domain crashes, and a logical corner case where resetting the vcpu with an oustanding waitqueue would crash the domain.
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
CC: Juergen Gross <[email protected]>
CC: Dario Faggioli <[email protected]>
--- xen/common/domain.c | 2 -- xen/common/sched/core.c | 4 +--- xen/common/wait.c | 23 ----------------------- xen/include/xen/sched.h | 1 - 4 files changed, 1 insertion(+), 29 deletions(-)
xen/common/domain.c +0 -2
@@ -1428,8 +1428,6 @@ int vcpu_reset(struct vcpu *v) v->is_initialised =0 ;if ( v->affinity_broken &VCPU_AFFINITY_OVERRIDE )vcpu_temporary_affinity (v,NR_CPUS ,VCPU_AFFINITY_OVERRIDE ); -if ( v->affinity_broken &VCPU_AFFINITY_WAIT ) -vcpu_temporary_affinity (v,NR_CPUS ,VCPU_AFFINITY_WAIT );clear_bit (_VPF_blocked, &v->pause_flags);clear_bit (_VPF_in_reset, &v->pause_flags);
xen/common/sched/core.c +1 -3
@@ -1610,12 +1610,10 @@ void watchdog_domain_destroy(struct domain *d)/* * Pin a vcpu temporarily to a specific CPU (or restore old pinning state if * cpu is NR_CPUS). -* Temporary pinning can be done due to two reasons, which may be nested: +* Temporary pinning can be done for a number of reasons, which may be nested: * - VCPU_AFFINITY_OVERRIDE (requested by guest): is allowed to fail in case * of a conflict (e.g. in case cpupool doesn't include requested CPU, or * another conflicting temporary pinning is already in effect. -* - VCPU_AFFINITY_WAIT (called by wait_event()): only used to pin vcpu to the -* CPU it is just running on. Can't fail if used properly. */ int vcpu_temporary_affinity (struct vcpu *v,unsigned int cpu,uint8_t reason) {
xen/common/wait.c +0 -23
@@ -127,16 +127,6 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)ASSERT (wqv->used ==0 ); -/* Save current VCPU affinity; force wakeup on *this* CPU only. */ -if (vcpu_temporary_affinity (curr,smp_processor_id (),VCPU_AFFINITY_WAIT ) ) - { -gdprintk (XENLOG_ERR ,"Unable to set vcpu affinity\n" ); -domain_crash (curr->domain); - -for ( ; ; ) -do_softirq (); - } -/* * Hand-rolled setjmp(). *
@@ -187,7 +177,6 @@ static void __prepare_to_wait(struct waitqueue_vcpu *wqv)static void __finish_wait (struct waitqueue_vcpu *wqv) { wqv->used =0 ; -vcpu_temporary_affinity (current,NR_CPUS ,VCPU_AFFINITY_WAIT ); }void check_wakeup_from_wait (void )
@@ -201,18 +190,6 @@ void check_wakeup_from_wait(void)if (likely (!wqv->used) )return ; -/* Check if we are still pinned. */ -if (unlikely (!(curr->affinity_broken &VCPU_AFFINITY_WAIT )) ) - { -gdprintk (XENLOG_ERR ,"vcpu affinity lost\n" ); -domain_crash (curr->domain); - -/* Re-initiate scheduler and don't longjmp(). */ -raise_softirq (SCHEDULE_SOFTIRQ ); -for ( ; ; ) -do_softirq (); - } -/* * Hand-rolled longjmp(). *
xen/include/xen/sched.h +0 -1
@@ -223,7 +223,6 @@ struct vcpu/* VCPU need affinity restored */ uint8_t affinity_broken;#define VCPU_AFFINITY_OVERRIDE 0x01 -#define VCPU_AFFINITY_WAIT 0x02/* A hypercall has been preempted. */ bool hcall_preempted;
Signature · 1 line
2.11.0
Re: [PATCH 5/5] xen/wait: Remove VCPU_AFFINITY_WAIT
Quoted 4 lines · Andrew Cooper
With the waitqueue logic updated to not use an absolute stack pointer reference, the vCPU can safely be resumed anywhere.
Remove
VCPU_AFFINITY_WAITcompletely, getting rid of two domain crashes,
I understand you mean two domain_crash() invocations here, but ...
Quoted 3 lines
and a
logical corner case where resetting the vcpu with an oustanding waitqueue would crash the domain.
... some other domain crash here?
Quoted 1 line
Signed-off-by Andrew Cooper <[email protected]>
I assume you've checked thoroughly that calling code hasn't grown dependencies on execution coming back on the same CPU?
Jan
Re: [PATCH 5/5] xen/wait: Remove VCPU_AFFINITY_WAIT
Quoted 11 lines · Jan Beulich
Quoted 4 lines · Andrew Cooper
With the waitqueue logic updated to not use an absolute stack pointer reference, the vCPU can safely be resumed anywhere.
Remove
VCPU_AFFINITY_WAITcompletely, getting rid of two domain crashes,I understand you mean two
domain_crash()invocations here, but ...Quoted 3 lines
and a
logical corner case where resetting the vcpu with an oustanding waitqueue would crash the domain.... some other domain crash here?
One of the two above. It's more that resetting (would have) broken the affinity and would have triggered the domain crash.
Quoted 4 lines
Quoted 2 lines
Signed-off-by Andrew Cooper <[email protected]>I assume you've checked thoroughly that calling code hasn't grown dependencies on execution coming back on the same CPU?
Urgh yes, my trivial test case didn't encounter it, but anything with an smp_processor_id() stashed on the stack is going to end up unhappy.
I'm going to have to retract half this series. (I'll follow up on the 0/$N with the longer term plan to remove this mess).
~Andrew
Quoted 9 lines · Andrew Cooper
This started out as patch 2 for a different task, and quickly identified some technical debt, long overdue for cleaning up.
Andrew Cooper (5):
xen/wait: Drop vestigial remnants ofTRAP_regs_partialxen/wait: Extend the description of how this logic actually works xen/wait: Minor asm improvements
xen/wait: Use relative stack adjustments
xen/wait: RemoveVCPU_AFFINITY_WAIT
While going through this series I came to notice that we build wait.c even on Arm, and I couldn't convince myself that wait_event() is actually not reachable there when e.g. there's an Arm-specific vm_event.c. I would generally prefer if non-functioning code paths were actually compiled out.
Thoughts?
Jan
Quoted 10 lines · Jan Beulich
Quoted 9 lines · Andrew Cooper
This started out as patch 2 for a different task, and quickly identified some technical debt, long overdue for cleaning up.
Andrew Cooper (5):
xen/wait: Drop vestigial remnants ofTRAP_regs_partialxen/wait: Extend the description of how this logic actually works xen/wait: Minor asm improvements
xen/wait: Use relative stack adjustments
xen/wait: RemoveVCPU_AFFINITY_WAIT
Quoted 6 lines
While going through this series I came to notice that we build
wait.ceven on Arm, and I couldn't convince myself thatwait_event()is actually not reachable there when e.g. there's an Arm-specificvm_event.c. I would generally prefer if non-functioning code paths were actually compiled out.Thoughts?
I've been wanting to delete wait.c fully for a long time.
It is only needed because the event/paging/access interfaces still use a single 4k shared ring, and even then, only when you happen to fill the 4k ring, which is 11 vCPUs on x86 last I checked.
I could easily believe that limit has never been tripped on ARM.
There are plenty of perf wins to be had by building a new Xen=>agent interface using acquire_resource, which include being able to guarantee that we never need to pause a vCPU to wait for space in the ring to post a event.
With the interface fixed, wait.c ceases to have any use whatsoever.
~Andrew