CPU 多核指令 —— WFE 原理【原创】

转自：http://tinylab.org/arm-wfe/

Zhang Binghua 创作于 2020/05/19

打赏

微信公众号		知识星球
	关注 @泰晓科技 与数千位一线 Linux 工程师做朋友，您准备好了吗？
周一到周五，天天有新文。		日更实战经验与技巧！

1 背景简介

大家好，我叫张昺华，中间那个字和“饼”字一个读音，本人非常热衷技术，是个技术狂热者。

今天我想分享一个跟多核锁原理相关的东西，由于我搞 arm 居多，所以目前只研究了 arm 架构下的 WFE 指令，分享出来，如果有表述不精准或者错误的地方还请大家指出，非常感谢。研究这个原因也是只是想搞清楚所以然和来龙去脉，以后写代码可以更游刃有余。

2 我与 WFE 的初次见面

偶然看 spin_lock 的 arm 架构下的 smp 源码的时候，发现了 wfe() 这个接口：

1. static inline void arch_spin_lock(arch_spinlock_t *lock)
2. {
3. unsigned long tmp;
4. u32 newval;
5. arch_spinlock_t lockval;
7. prefetchw(&lock->slock);
8. __asm__ __volatile__(
9. "1: ldrex %0, [%3]\n"
10. " add %1, %0, %4\n"
11. " strex %2, %1, [%3]\n"
12. " teq %2, #0\n"
13. " bne 1b"
14. : "=&r" (lockval), "=&r" (newval), "=&r" (tmp)
15. : "r" (&lock->slock), "I" (1 << TICKET_SHIFT)
16. : "cc");
18. while (lockval.tickets.next != lockval.tickets.owner) {
19. wfe();
20. lockval.tickets.owner = READ_ONCE(lock->tickets.owner);
21. }
23. smp_mb();
24. }

我印象之前的 kernel 是没有这个 wfe 这个函数的，当 cpu0 获取到锁后，如果 cpu1 再想获取锁，此时会被 lock 住，然后进入死等的状态，那么 wfe 这个指令的作用是会让 cpu 进入 low power standby，这样可以降低功耗，本来发生竞态时其他的 cpu 都要等待这个锁释放才能运行，有了这个指令，相当于是“因祸得福”了，还可以降低功耗，当然这是有条件的，后面追溯并研究了一下 wfe 这个指令的作用。

3 spinlock 与 WFE、SEV、WFI

首先 spin_lock 函数，搞内核的大家都知道，那么我把 linux-stable 的代码黏贴出来如下：

1. static __always_inline void spin_lock(spinlock_t *lock)
2. {
3. raw_spin_lock(&lock->rlock);
4. }
6. #define raw_spin_lock(lock) _raw_spin_lock(lock)
8. #ifndef CONFIG_INLINE_SPIN_LOCK
9. void __lockfunc _raw_spin_lock(raw_spinlock_t *lock)
10. {
11. __raw_spin_lock(lock);
12. }
13. EXPORT_SYMBOL(_raw_spin_lock);
14. #endif
16. static inline void __raw_spin_lock(raw_spinlock_t *lock)
17. {
18. preempt_disable();
19. spin_acquire(&lock->dep_map, 0, 0, _RET_IP_);
20. LOCK_CONTENDED(lock, do_raw_spin_trylock, do_raw_spin_lock);
21. }
23. /*
24. * We are now relying on the NMI watchdog to detect lockup instead of doing
25. * the detection here with an unfair lock which can cause problem of its own.
26. */
27. void do_raw_spin_lock(raw_spinlock_t *lock)
28. {
29. debug_spin_lock_before(lock);
30. arch_spin_lock(&lock->raw_lock);
31. mmiowb_spin_lock();
32. debug_spin_lock_after(lock);
33. }
36. /*
37. * ARMv6 ticket-based spin-locking.
38. *
39. * A memory barrier is required after we get a lock, and before we
40. * release it, because V6 CPUs are assumed to have weakly ordered
41. * memory.
42. */
44. static inline void arch_spin_lock(arch_spinlock_t *lock)
45. {
46. unsigned long tmp;
47. u32 newval;
48. arch_spinlock_t lockval;
50. prefetchw(&lock->slock);
51. __asm__ __volatile__(
52. "1: ldrex %0, [%3]\n"
53. " add %1, %0, %4\n"
54. " strex %2, %1, [%3]\n"
55. " teq %2, #0\n"
56. " bne 1b"
57. : "=&r" (lockval), "=&r" (newval), "=&r" (tmp)
58. : "r" (&lock->slock), "I" (1 << TICKET_SHIFT)
59. : "cc");
61. while (lockval.tickets.next != lockval.tickets.owner) {
62. wfe();
63. lockval.tickets.owner = READ_ONCE(lock->tickets.owner);
64. }
66. smp_mb();
67. }

对于 arm32：

1. #if __LINUX_ARM_ARCH__ >= 7 || \
2. (__LINUX_ARM_ARCH__ == 6 && defined(CONFIG_CPU_32v6K))
3. #define sev() __asm__ __volatile__ ("sev" : : : "memory")
4. #define wfe() __asm__ __volatile__ ("wfe" : : : "memory")
5. #define wfi() __asm__ __volatile__ ("wfi" : : : "memory")
6. #else
7. #define wfe() do { } while (0)
8. #endif

对于 arm64：

1. #define sev() asm volatile("sev" : : : "memory")
2. #define wfe() asm volatile("wfe" : : : "memory")
3. #define wfi() asm volatile("wfi" : : : "memory")
5. static inline void arch_spin_unlock(arch_spinlock_t *lock)
6. {
7. smp_mb();
8. lock->tickets.owner++;
9. dsb_sev();
10. }
11. #define SEV __ALT_SMP_ASM(WASM(sev), WASM(nop))
13. static inline void dsb_sev(void)
14. {
16. dsb(ishst);
17. __asm__(SEV);
18. }
20. #ifdef CONFIG_SMP
21. #define __ALT_SMP_ASM(smp, up) \
22. "9998: " smp "\n" \
23. " .pushsection \".alt.smp.init\", \"a\"\n" \
24. " .long 9998b\n" \
25. " " up "\n" \
26. " .popsection\n"
27. #else
28. #define __ALT_SMP_ASM(smp, up) up
29. #endif

以上我们可以看出，在 lock 的时候使用 WFE，在 unlock 的时候使用 SEV，这个必须要成对使用，原因我下面会说。

对于内核版本 Linux 3.0.56：

1. static inline void arch_spin_lock(arch_spinlock_t *lock)
2. {
3. unsigned long tmp;
5. __asm__ __volatile__(
6. "1: ldrex %0, [%1]\n"
7. " teq %0, #0\n"
8. WFE("ne")
9. " strexeq %0, %2, [%1]\n"
10. " teqeq %0, #0\n"
11. " bne 1b"
12. : "=&r" (tmp)
13. : "r" (&lock->lock), "r" (1)
14. : "cc");
16. smp_mb();
17. }

对于 Linux 2.6.18：

1. define _raw_spin_lock(lock) __raw_spin_lock(&(lock)->raw_lock)
3. static inline void __raw_spin_lock(raw_spinlock_t *lock)
4. {
5. unsigned long tmp;
7. __asm__ __volatile__(
8. "1: ldrex %0, [%1]\n"
9. " teq %0, #0\n"
10. " strexeq %0, %2, [%1]\n"
11. " teqeq %0, #0\n"
12. " bne 1b"
13. : "=&r" (tmp)
14. : "r" (&lock->lock), "r" (1)
15. : "cc");
17. smp_mb();
18. }

以上大家可以看出，最早期的 kernel 版本是没有 wfe 这条指令的，后面的版本才有。

4 WFE、SEV 与 WFI 的作用与工作原理

那这条指令的作用是什么呢？我们可以上 arm 官网去查看这条指令的描述：ARM Software development tools

• SEV

  SEV causes an event to be signaled to all cores within a multiprocessor system. If SEV is implemented, WFE must also be implemented.

SEV 指令可以产生事件信号，发送给全部的 cpu，让他们唤醒。如果 SEV 实现了，那么 WFE 也必须被实现。这里的事件信号其实会表现为 Event register，这是个一 bit 的 register，如果有事件，那么此 bit 为真。

• WFE

If the Event Register is not set, WFE suspends execution until one of the following events occurs:

• an IRQ interrupt, unless masked by the CPSR I-bit • an FIQ interrupt, unless masked by the CPSR F-bit • an Imprecise Data abort, unless masked by the CPSR A-bit • a Debug Entry request, if Debug is enabled • an Event signaled by another processor using the SEV instruction.

If the Event Register is set, WFE clears it and returns immediately. If WFE is implemented, SEV must also be implemented.

对于 WFE，如果 Event Register 没有设置，WFE 会让 cpu 进入 low-power state，直到下面列举的五个 events 产生，比如说中断等等都会唤醒当前因为 WFE 而 suspend 的cpu。

如果 Event Register 被设置了，那么 WFE 会直接返回，不让 cpu 进入low-power state，目的是因为既然有事件产生了，说明当前 cpu 需要干活，不能 suspend，所以才这样设计。

这里我很好奇 Event Register 到底是怎么理解的。因此需要阅读手册《ARM Architecture Reference Manual.pdf》，下面我会做说明。

• WFI

WFI suspends execution until one of the following events occurs:

• an IRQ interrupt, regardless of the CPSR I-bit • an FIQ interrupt, regardless of the CPSR F-bit • an Imprecise Data abort, unless masked by the CPSR A-bit • a Debug Entry request, regardless of whether Debug is enabled.

而对于 WFI 这种，不会判断 Event register，暴力的直接让 cpu 进入 low-power state，直到有上述四个 events 产生才会唤醒 cpu。

注意，这里 WFE 比 WFI 多了一个唤醒特性：

an Event signaled by another processor using the SEV instruction.

也就是说 SEV 是不会唤醒 WFI 指令休眠的 cpu 的。这点需要特别注意。

接下来我谈下这个 Event Register 是怎么回事了。看这个文档《ARM Architecture Reference Manual.pdf》

• The Event Register

The Event Register is a single bit register for each processor. When set, an event register indicates that an event has occurred, since the register was last cleared, that might require some action by the processor. Therefore, the processor must not suspend operation on issuing a WFE instruction.

The reset value of the Event Register is UNKNOWN.

The Event Register is set by:

• an SEV instruction • an event sent by some IMPLEMENTATION DEFINED mechanism • a debug event that causes entry into Debug state • an exception return.

As shown in this list, the Event Register might be set by IMPLEMENTATION DEFINED mechanisms. The Event Register is cleared only by a Wait For Event instruction. Software cannot read or write the value of the Event Register directly.

以上就是 Event Register 的表述，上述已经说的很明白了，Event Register 只有一个 bit，可以被 set 的情况总有四种大类型。当任意一个条件满足的时候，Event Register 都可以被 set，那么当 WFE 进入的时候会进行 Event Register 的判断，如果为真，就直接返回。

再来看看 WFE 的介绍：

Wait For Event is a hint instruction that permits the processor to enter a low-power state until one of a number of events occurs, including events signaled by executing the SEV instruction on any processor in the multiprocessor system. For more information, see Wait For Event and Send Event on page B1-1197.

In an implementation that includes the Virtualization Extensions, if HCR.TWE is set to 1, execution of a WFE instruction in a Non-secure mode other than Hyp mode generates a Hyp Trap exception if, ignoring the value of the HCR.TWE bit, conditions permit the processor to suspend execution. For more information see Trapping use of the WFI and WFE instructions on page B1-1249.

接下来上 WFE 这条指令的伪代码流程：

1. Assembler syntax
2. WFE{<c>}{<q>}
3. where:
4. <c>, <q> See Standard assembler syntax fields on page A8-285.
5. Operation
6. if ConditionPassed() then
7. EncodingSpecificOperations();
8. if EventRegistered() then
9. ClearEventRegister();
10. else
11. if HaveVirtExt() && !IsSecure() && !CurrentModeIsHyp() && HCR.TWE == '1' then
12. HSRString = Zeros(25);
13. HSRString<0> = '1';
14. WriteHSR('000001', HSRString);
15. TakeHypTrapException();
16. else
17. WaitForEvent();
18. Exceptions
19. Hyp Trap.

看了上面这段 WFE 的伪代码，一目了然，首先判断 ConditionPassed()，这些函数大家可以在 arm 手册中查看其详细含义，如果 EventResigerted() 函数为真，也就是这个 1 bit 的寄存器为真，那么就清除此 bit，然后退出返回，不会让 cpu 进入 low power state；

如果不是异常处理，TakeHypTrapException()，那么就 WaitForEvent()，等待唤醒事件到来，到来了，就唤醒当前 cpu。

为什么有事件来了就直接返回呢，因为 WFE 的设计认为，如果此时有 event 事件，那么说明当前 cpu 要干活，那就没必要进入 low power state 模式。

如果没有事件产生，那么就可以进入 low power state 模式，因为 cpu 反正也是在等待锁，此时也干不了别的事情，还不如休眠还可以降低功耗。

当然，irq，fiq 等很多中断都可以让 WFE 休眠的 cpu 唤醒，那么这样做还有什么意义呢？比如说时钟中断是一直产生的，那么 cpu 很快就醒了啊，都不用等到发 SEV，那么既然是用 spin_lock，也可以在中断上半部使用，也可以在进程上下文，既然是自旋锁，就意味着保护的这段代码是要足够精简，不希望被其他东西打断，那么如果你保护的这部分代码非常长，这时候整个系统响应很可能会变慢，因为如果这时候有人也要使用这个锁的话，那么是否保护的这段代码设计上是有问题的。因此用 spin_lock 保护的函数尽可能要短，如果长的话可能需要换其他锁，或者考虑下是否真的要这么长的保护措施。

TakeHypTrapException()，是进入异常处理

1. Pseudocode description of taking the Hyp Trap exception
2. The TakeHypTrapException() pseudocode procedure describes how the processor takes the exception:
3. // TakeHypTrapException()
4. // ======================
5. TakeHypTrapException()
6. // HypTrapException is caused by executing an instruction that is trapped to Hyp mode as a
7. // result of a trap set by a bit in the HCR, HCPTR, HSTR or HDCR. By definition, it can only
8. // be generated in a Non-secure mode other than Hyp mode.
9. // Note that, when a Supervisor Call exception is taken to Hyp mode because HCR.TGE==1, this
10. // is not a trap of the SVC instruction. See the TakeSVCException() pseudocode for this case.
11. preferred_exceptn_return = if CPSR.T == '1' then PC-4 else PC-8;
12. new_spsr_value = CPSR;
13. EnterHypMode(new_spsr_value, preferred_exceptn_return, 20);
14. Additional pseudocode functions for exception handling on page B1-1221 defines the EnterHypMode() pseudocode
15. procedure.

ClearEventRegister()

Clear the Event Register of the current processor 清除Event Register的bit

EventRegistered()

Determine whether the Event Register of the current processor is set Event Register bit为真，即被设置过

WaitForEvent()

Wait until WFE instruction completes

等待 Events 事件，有任何一个 Event 事件来临，都会唤醒当前被 WFE suspend 下去的 cpu， 如果是 SEV，会唤醒全部被 WFE suspend 下去的cpu。

如下是关于 WFE 的 wake up events 事件描述和列举：

WFE wake-up events

The following events are WFE wake-up events:

• the execution of an SEV instruction on any processor in the multiprocessor system • a physical IRQ interrupt, unless masked by the CPSR.I bit • a physical FIQ interrupt, unless masked by the CPSR.F bit • a physical asynchronous abort, unless masked by the CPSR.A bit • in Non-secure state in any mode other than Hyp mode: — when HCR.IMO is set to 1, a virtual IRQ interrupt, unless masked by the CPSR.I bit — when HCR.FMO is set to 1, a virtual FIQ interrupt, unless masked by the CPSR.F bit — when HCR.AMO is set to 1, a virtual asynchronous abort, unless masked by the CPSR.A bit • an asynchronous debug event, if invasive debug is enabled and the debug event is permitted • an event sent by the timer event stream, see Event streams on page B8-1934 • an event sent by some IMPLEMENTATION DEFINED mechanism.

In addition to the possible masking of WFE wake-up events shown in this list, when invasive debug is enabled and DBGDSCR[15:14] is not set to 0b00, DBGDSCR.INTdis can mask interrupts, including masking them acting as WFE wake-up events. For more information, see DBGDSCR, Debug Status and Control Register on page C11-2206. As shown in the list of wake-up events, an implementation can include IMPLEMENTATION DEFINED hardware mechanisms to generate wake-up events. NoteFor more information about CPSR masking see Asynchronous exception masking on page B1-1181. If the configuration of the masking controls provided by the Security Extensions, or Virtualization Extensions, mean that a CPSR mask bit cannot mask the corresponding exception, then the physical exception is a WFE wake-up event, regardless of the value of the CPSR mask bit.

接下来我们看下 WFI 的伪代码：

1. Assembler syntax
2. WFI{<c>}{<q>}
3. where:
4. <c>, <q> See Standard assembler syntax fields on page A8-285.
5. Operation
6. if ConditionPassed() then
7. EncodingSpecificOperations();
8. if HaveVirtExt() && !IsSecure() && !CurrentModeIsHyp() && HCR.TWI == '1' then
9. HSRString = Zeros(25);
10. HSRString<0> = '1';
11. WriteHSR('000001', HSRString);
12. TakeHypTrapException();
13. else
14. WaitForInterrupt();
15. Exceptions
16. Hyp Trap.

相关解释：

WFI

Wait For Interrupt is a hint instruction that permits the processor to enter a low-power state until one of a number of asynchronous events occurs. For more information, see Wait For Interrupt on page B1-1200. In an implementation that includes the Virtualization Extensions, if HCR.TWI is set to 1, execution of a WFE instruction in a Non-secure mode other than Hyp mode generates a Hyp Trap exception if, ignoring the value of the HCR.TWI bit, conditions permit the processor to suspend execution. For more information see Trapping use of the WFI and WFE instructions on page B1-1249.

以上我们可以看出，WFI 并没有去判断 event register，因此看伪代码可以很直观的看出 WFI 与 WFE 的区别。

以上是我个人的理解，如果有表述不精准或者不准确的地方还请大家指出，欢迎交流。

5 参考资料

• ARM 架构下 spinlock 原理 (代码解读)
• ARM WFI 和 WFE 指令
• ARM Software development tools
• Linux 内核自旋锁 spinlock_t 机制

---

猜你喜欢：

• 知识星球：独家 Linux 实战经验与技巧，订阅「Linux知识星球」
• 儒码科技：Linux 技术咨询、培训与服务，联系「儒码科技」
• 技术交流：Linux 用户技术交流微信群，联系微信号：tinylab

支付宝打赏		微信打赏
	请作者喝杯咖啡吧

Read Related:

• 开源硬件迎来 8 核时代
• Linux 汇编语言快速上手：4大架构一块学

Read Latest:

• 泰晓资讯·5月 / 第三期 / 2020
• Linux Lab 发布 v0.4 rc3，新增 ARM64 Uboot 支持
• Linux Lab：难以抗拒的十大理由 V2.0
• Linux 下的 Sync 卡死问题分析报告
• 泰晓资讯·5月 / 第二期 / 2020

---

• ARM 4

• WFE 1
• SEV 1
• WFI 1
• SMP 1
• 自旋锁 1
• 低功耗 1

---

本作品由 Zhang Binghua 创作，采用 CC BY-NC-ND 4.0 协议 进行许可。未经授权，谢绝商业使用！

 

 

Zhang Binghua (sky)

对 Linux 内核代码极度热爱，喜欢和周边的小伙伴们一起讨论研究各种技术

—— 扫码访问作者Github